-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
feat: LEAP-1599: Allow to edit TimelineRegion spans #6577
Conversation
Make `TimelineRegion` fields editable, but with new form to display the editor in this case — `start`/`end` are in the `ranges[0]`, not in region itself. New editor is pretty simple and reuses styles from both audio region and image region editors.
✅ Deploy Preview for heartex-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for label-studio-docs-new-theme ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Correct instant detection, correct distinguishing between start and end. The issue was that if lifespan is bigger than screen then start or end might not be rendered.
web/libs/editor/src/components/SidePanels/DetailsPanel/RegionEditor.tsx
Outdated
Show resolved
Hide resolved
web/libs/editor/src/components/SidePanels/DetailsPanel/RegionEditor.tsx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, I added a couple suggestions/questions surrounding the type propagation.
/git merge
|
/git merge
|
Make
TimelineRegion
fields editable, but with new form to display the editor in this case —start
/end
are in theranges[0]
, not in region itself. New editor is pretty simple and reuses styles from both audio region and image region editors.Also added an icon for timeline spans.
PR fulfills these requirements
Change has impacts in these area(s)
Describe the reason for change
Timeline spans can only be drawn within visible area and they can't be changed after. So we are adding ability to increase/change them at least via the start/end editable fields.
What alternative approaches were there?
Allow to change spans on timeline, but that's much more effort and more complex UX.
Does this PR introduce a breaking change?
What level of testing was included in the change?