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 GET /shows/{id} Endpoint for Retrieving a Show by ID #4

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

Implement GET /shows/{id} Endpoint for Retrieving a Show by ID #4

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:

The task involves implementing a GET endpoint to retrieve a specific show based on its unique ID. This endpoint will provide a detailed representation of the show, including its title, start and end dates, live status, and associated moderators.

Tasks:

  • Set up the route and controller for the GET /shows/{id} endpoint.
  • Validate the id parameter to ensure it corresponds to an existing show.
  • Retrieve the show details from the database based on the provided id.
  • Serialize the show data in accordance with the specified response format.
  • Handle cases where the requested show is not found and return an appropriate error response.

Additional Considerations:

  • Ensure that the response follows the defined Swagger/OpenAPI specification for the GET /shows/{id} endpoint.
  • Implement proper error handling and response codes for various scenarios (e.g., show not found, server error).
  • Write unit tests to validate the functionality of the endpoint.

Acceptance Criteria:

  • The GET /shows/{id} endpoint successfully retrieves and returns the details of the specified show.
  • Proper error responses are provided in case of invalid or non-existent show IDs.
@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