-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Dependencies
Complete the following issues first:
- Create fixtures for Articles
- Form Component for Articles
- Copy Placeholders for
Articles
pages; add to App.js/AppNavbar.js
Acceptance Criteria:
-
When you navigate to
/articles/create
in the URL bar,
there is page that allows the user to create a new Articles record. -
When you enter data into the form and click the submit button,
if the data is valid, the data is sent to the server,
a new Articles record is created,and the user is routed to the
/articles
route for theArticlesIndexPage
page. -
When you enter data into the form and click the submit button,
if the data is not valid,appropriate error messages are displayed,
the data is NOT sent to the server, a new Articles record is NOT created,
and the user remains on thearticles/create
page. -
When you submit valid data to the page and click submit, a new valid database
entry is stored in the database. (You can verify this by using the swagger
endpoint to view the current data in the table.) -
The PR description has step-by-step descriptions for testing the new page, along
with screenshots, so that someone reviewing the PR will know what to do to test
it, and what it is supposed to look like when it functions correctly. -
The PR description has a link to the storybook entry for the new page.
Implementation Details
-
Before starting, refamiliarize yourself with the backend CRUD API endpoints for
Articles
by looking at the swagger page. You are going to be copy/pasting
code from theRestaurant
andUCSBDates
components. Those use backend api endpoints
that are similar to the ones forArticles
, but not identical. You will need
to know the exact name of the API endpoints forArticles
in order to
be sure that your frontend code is calling the correct backend endpoints. -
In
ArticlesCreatePage.js
, replace the code fromPlaceholderCreatePage.js
with code modelled after the filesRestaurantCreatePage.js
and/orUCSBDatesCreatePage.js
that is appropriate to yourArticles
table. Be sure to get the API endpoint names correct for yourArticles
table. -
In
ArticlesCreatePage.test.js
, replace the code fromPlaceholderCreatePage.test.js
with code modelled after the filesRestaurantCreatePage.test.js
and/orUCSBDatesCreatePage.test.js
appropriate to yourArticles
table. Be sure to get the API endpoint names correct for yourArticles
table. -
Under
frontend/src/stories/pages/Articles/
create a file calledArticlesCreatePage.stories.js
modelled after the filesRestaurantCreatePage.stories.js
and/orUCSBDatesCreatePage.stories.js
.
Reminders (all from frontend
directory):
- Always start by setting your node version with
nvm use 20.17.0
- To run storybook locally:
npm run storybook
. - To run tests locally:
npm test
. - Quickly test coverage locally:
npm run coverage
- Check linting locally:
npx eslint --fix .
- Check mutation coverage locally (slow):
npx stryker run
- Check mutation coverage of single file (faster):
npx stryker run -m src/main/pages/Articles/ArticlesCreatePage.js
What to do next
- Do a PR (following the usual steps).
- Check for other PRs
- Start work on "Index Page for
Articles
plus tests and stories"(following the usual steps for a new issue)