This issue should be completed after the issue with the title "Create RecommendationRequestController..."
Overview
In this issue, we add one more method from the example Controller used as a basis for our code; namely the method with the annotation shown below:
Annotation
Purpose
@DeleteMapping("")
Delete a single record from the table; use the value passed in as a @RequestParam to do a lookup by id. If a matching row is not found, throw an EntityNotFoundException.
You'll need to copy over the code for the DELETE method from the example controller,
and then paste those into RecommendationRequestController.java and edit them to match your database table.
Then, copy over the tests that pertain to the DELETE method from the example controller,
paste those into RecommendationRequestControllerTests.java and edit them to match your database table.
Acceptance Criteria:
[x] In RecommendationRequestController.java there is code for an
endpoint DELETE /api/RecommendationRequest?id=123 endpoint
that deletes the record if it exists, and returns 200 (ok) and
the text record 123 deleted, or returns 404 (Not Found) and
the text record 123 not found if it does not.
[x] The Swagger-UI endpoints for this endpoint is well documented
so that any member of the team can understand how to use it.
[x] The endpoint works as expected on localhost.
[x] The endpoint works as expected when deployed to Dokku.
[x] There is full test coverage (Jacoco) for the new code in
RecommendationRequestController.java
[x] There is full mutation test coverage (Pitest) for new code in
RecommendationRequestController.java
What to do next
Do a PR, following all of the usual steps (title, description, Closes #n text,
dragging issue to "In Review", requesting reviewers).
Check to see if any fellow team members PRs need to be reviewed.
Then, assign yourself the next incomplete issue for your database table (RecommendationRequest)
Follow all the usual steps (assign to self, drag to "In Progress", start new branch.)
When you are done with all issues for RecommendationRequest, please give your full attention to
helping others on your team to complete the sprint, so that the team
is ready to submit on Canvas by the deadline.
Dependencies
This issue should be completed after the issue with the title "Create
RecommendationRequestController
..."Overview
In this issue, we add one more method from the example Controller used as a basis for our code; namely the method with the annotation shown below:
@DeleteMapping("")
@RequestParam
to do a lookup by id. If a matching row is not found, throw anEntityNotFoundException
.You'll need to copy over the code for the DELETE method from the example controller, and then paste those into
RecommendationRequestController.java
and edit them to match your database table.Then, copy over the tests that pertain to the DELETE method from the example controller, paste those into
RecommendationRequestControllerTests.java
and edit them to match your database table.Acceptance Criteria:
RecommendationRequestController.java
there is code for an endpointDELETE /api/RecommendationRequest?id=123
endpoint that deletes the record if it exists, and returns 200 (ok) and the textrecord 123 deleted
, or returns 404 (Not Found) and the textrecord 123 not found
if it does not.RecommendationRequestController.java
RecommendationRequestController.java
What to do next
Do a PR, following all of the usual steps (title, description,
Closes #n
text, dragging issue to "In Review", requesting reviewers).Check to see if any fellow team members PRs need to be reviewed.
Then, assign yourself the next incomplete issue for your database table (
RecommendationRequest
)Follow all the usual steps (assign to self, drag to "In Progress", start new branch.)
When you are done with all issues for
RecommendationRequest
, please give your full attention to helping others on your team to complete the sprint, so that the team is ready to submit on Canvas by the deadline.