feat: implement CRUD API endpoints for user stream bookmarks#591
Merged
Conversation
|
@T-kesh is attempting to deploy a commit to the david's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
@T-kesh Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Contributor
Author
|
@davedumto Please review this |
Contributor
Author
|
@davedumto Please review this |
Contributor
Author
|
@davedumto Kindly review |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR implements the personal stream markers API, enabling viewers to save private bookmarks at specific timestamps during VOD playback. The new endpoints, located under
app/api/routes-f/stream/markers/, allow users to fetch their own markers for a specific recording, add new markers with optional notes (up to 100 characters), and delete existing ones by ID. To ensure a performant and reliable experience, the implementation enforces a limit of 50 markers per user per recording and leverages server-side session verification for strict privacy. Additionally, the routes include self-contained database initialization logic to automatically manage thestream_markerstable and indices, ensuring the feature is fully standalone and easy to deploy.closes #522