-
-
Notifications
You must be signed in to change notification settings - Fork 359
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
Delete videos endpoint #467
Labels
Comments
2 tasks
Dedekind561
changed the title
Implement the
Implement the **delete videos** endpoint
Apr 3, 2024
DELETE /api/videos
endpoint
Dedekind561
changed the title
Implement the **delete videos** endpoint
Implement the *delete videos* endpoint
Apr 3, 2024
Dedekind561
changed the title
Implement the *delete videos* endpoint
Implement the delete videos endpoint
Apr 3, 2024
Dedekind561
changed the title
Implement the delete videos endpoint
Delete videos endpoint
Apr 3, 2024
3 tasks
This was referenced Apr 25, 2024
This was referenced Apr 29, 2024
This was referenced May 4, 2024
This was referenced May 4, 2024
This was referenced May 13, 2024
3 tasks
2 tasks
Open
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 code204
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 HTTP404
status 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
).204
to indicate successful deletion.The text was updated successfully, but these errors were encountered: