Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement DELETE /shows/{id} Endpoint for Deleting a Show by ID #6

Open
4 tasks
Lapotor opened this issue Nov 1, 2023 · 0 comments · May be fixed by #103
Open
4 tasks

Implement DELETE /shows/{id} Endpoint for Deleting a Show by ID #6

Lapotor opened this issue Nov 1, 2023 · 0 comments · May be fixed by #103
Assignees
Milestone

Comments

@Lapotor
Copy link
Collaborator

Lapotor commented Nov 1, 2023

Description:

This task involves implementing the DELETE /shows/{id} endpoint, which allows the deletion of a specific show based on its unique identifier (id). This endpoint will handle the removal of the show from the database, ensuring that it is no longer accessible through the API.

Tasks:

  • Set up the route and controller method for handling the DELETE request.
  • Validate the id parameter to ensure it corresponds to a valid show.
  • Implement the logic to delete the show from the database.
  • Return the appropriate HTTP response indicating the success of the deletion operation.

Acceptance Criteria:

  • A successful DELETE request to /shows/{id} results in the specified show being permanently removed from the database.
  • An unsuccessful request (due to invalid id, server error, or other reasons) results in an appropriate error response being returned.

Additional Information:

  • Ensure proper error handling and response messages are implemented for various scenarios, such as invalid id, server errors, or any other potential issues.
  • Write unit tests to verify the correctness and robustness of the delete operation.
@Lapotor Lapotor added this to the v1.0.0 milestone Nov 1, 2023
@Lapotor Lapotor linked a pull request Dec 29, 2023 that will close this issue
@Lapotor Lapotor self-assigned this Dec 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant