From Full-Stack-Project-Assessment created by Dedekind561: CodeYourFuture/Full-Stack-Project-Assessment#467
Description
HTTP Method: DELETE
Route: /api/videos/{id}
This endpoint is used to delete a specific video from the database. DELETE endpoints don't require a request body, and they don't even need to return a response body! While you can return a confirmation message: however, if you don't want to, you can use the HTTP status code 204 to tell the client that the action was successful, but there is no response body.
To make the endpoint nicer, you can also change it so if you try to call this endpoint on an id that doesn't exist, the system may respond with a HTTP 404 status code designating that the video did not exist in the first place or was already deleted.
Acceptance Criteria
[ ] A DELETE /api/videos/{id} backend endpoint is implemented to remove specific videos.
[ ] The endpoint handles non-existent video IDs gracefully, returning an appropriate HTTP status code (e.g., 404).
[ ] The endpoint returns a confirmation message or uses an HTTP status code 204 to indicate successful deletion.
From Full-Stack-Project-Assessment created by Dedekind561: CodeYourFuture/Full-Stack-Project-Assessment#467
Description
HTTP Method:
DELETERoute:
/api/videos/{id}This endpoint is used to delete a specific video from the database.
DELETEendpoints don't require a request body, and they don't even need to return a response body! While you can return a confirmation message: however, if you don't want to, you can use the HTTP status code204to tell the client that the action was successful, but there is no response body.To make the endpoint nicer, you can also change it so if you try to call this endpoint on an
idthat doesn't exist, the system may respond with a HTTP404status code designating that the video did not exist in the first place or was already deleted.Acceptance Criteria
DELETE /api/videos/{id}backend endpoint is implemented to remove specific videos.404).204to indicate successful deletion.