Do the "Create personal dokku dev deployment" issue first.
Acceptance Criteria:
[ ] Backend API routes for CRUD operations for Articles are
available in Swagger (following the criteria from team02)
Implementation Details:
[ ] Find Articles.java in your team02 project in the directory
src/main/java/edu/ucsb/cs156/example/entities
and copy it into your team02 project in the same directory.
[ ] Do the same for ArticlesRepository.java from the directory
src/main/java/edu/ucsb/cs156/example/repositorires
[ ] Do the same for ArticlesController.java from the directory
src/main/java/edu/ucsb/cs156/example/controllers
[ ] Do the same for ArticlesControllerTests.java from the directory
src/test/java/edu/ucsb/cs156/example/controllers
[ ] Do the same for your database migration file for $Articles, under /src/main/resources/db/migration/changes
[ ] With these files in place, visit swagger and make sure
the CRUD operations for Articles are working properly.
What to do next
Make a PR: When you've met all of the acceptance criteria, do a PR for this branch,
being sure to enter a reasonable title
and description.
In the description, include the text "Closes #n" where n is the number of
this issue.
It is also helpful to include a screenshot of the Swagger endpoints so that
the person reviewing your PR knows what to test. It is helpful to
deploy your branch to your dokku dev instance, and include a link to the
swagger page on your dokku instance.
Then ask for a team member to review your PR.
Finally: drag this issue from "In Progress" to "In Review".
Review Others' PRs: Next, see if there are any PRs that need to be code reviewed and merged. Unless you are the
first person on your team to complete a PR, there likely is at least one.
See:
Dependencies
Do the "Create personal dokku dev deployment" issue first.
Acceptance Criteria:
Articlesare available in Swagger (following the criteria from team02)Implementation Details:
Articles.javain your team02 project in the directorysrc/main/java/edu/ucsb/cs156/example/entitiesand copy it into your team02 project in the same directory.ArticlesRepository.javafrom the directorysrc/main/java/edu/ucsb/cs156/example/repositoriresArticlesController.javafrom the directorysrc/main/java/edu/ucsb/cs156/example/controllersArticlesControllerTests.javafrom the directorysrc/test/java/edu/ucsb/cs156/example/controllers/src/main/resources/db/migration/changesArticlesare working properly.What to do next
Make a PR: When you've met all of the acceptance criteria, do a PR for this branch, being sure to enter a reasonable title and description.
In the description, include the text "Closes #n" where
nis the number of this issue.It is also helpful to include a screenshot of the Swagger endpoints so that the person reviewing your PR knows what to test. It is helpful to deploy your branch to your dokku dev instance, and include a link to the swagger page on your dokku instance.
Then ask for a team member to review your PR.
Finally: drag this issue from "In Progress" to "In Review".
Review Others' PRs: Next, see if there are any PRs that need to be code reviewed and merged. Unless you are the first person on your team to complete a PR, there likely is at least one. See:
Start your next issue: Then, find the issue for "Create fixtures for
Articles" on the Kanban board in the ToDo column.