-
Notifications
You must be signed in to change notification settings - Fork 3.2k
fix: FIT-1059: Not sure 'Created' is the right name for the annotation state, perhaps 'Initial' could make more sense, take a look at the screenshot #8904
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
Conversation
…n state, perhaps 'Initial' could make more sense, take a look at the screenshot
✅ Deploy Preview for label-studio-storybook canceled.
|
✅ Deploy Preview for label-studio-playground canceled.
|
✅ Deploy Preview for heartex-docs canceled.
|
✅ Deploy Preview for label-studio-docs-new-theme canceled.
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #8904 +/- ##
===========================================
+ Coverage 66.35% 66.46% +0.11%
===========================================
Files 789 828 +39
Lines 63529 64783 +1254
Branches 10810 11040 +230
===========================================
+ Hits 42153 43059 +906
- Misses 21376 21720 +344
- Partials 0 4 +4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
/git merge
|
This pull request introduces improvements to how FSM (Finite State Machine) states are handled for tasks that are bulk-created, ensuring their state is properly initialized even when the usual model save hooks are bypassed. Additionally, it updates the label for the initial task state in the UI for clarity.
before:

after:

FSM state handling improvements:
_backfill_fsm_statesmethod inlabel_studio/tasks/serializers.pyto manually initialize FSM states for tasks created viabulk_create(), ensuring that FSM transitions registered withtriggers_on_create=Trueare properly set even when the model'ssave()method isn't called. This includes robust error handling and logging to avoid interrupting imports if FSM backfill fails for any task or batch.UI label update:
CREATEDstate from "Created" to "Initial" instate-registry.tsto better reflect its meaning in the UI.