Implement Scene Segments to mark and organize video sections (#3530)Feature/scene segments #6439
Conversation
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 Scene Segments feature requested in Issue #3530 and completes all required functionality for the associated bounty. It introduces a new SceneSegment model along with the necessary database migration, updates the schema, and adds full GraphQL support for creating, updating, and deleting scene segments. Validation has been implemented to ensure segment start and end times are logical (start is non-negative and always less than end). The database migration was verified to work correctly, and all GraphQL mutations (sceneSegmentCreate, sceneSegmentUpdate, and sceneSegmentDestroy) were tested successfully to confirm proper behavior and constraint enforcement. With these changes complete and verified, this PR is submitted to claim the $450 bounty for the feature.