-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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-1709: Add region index displaying to relations list #6941
Open
Gondragos
wants to merge
11
commits into
develop
Choose a base branch
from
fb-leap-1709/region-index-in-relations
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
Added a new region index element in the details panel with corresponding styles for alignment and visibility. Updated margin and layout adjustments for consistent design across elements. Introduced gap styling in relations panel for better spacing of node elements.
Region indices are now set consistently during sorting and creation. Removed redundant region index assignment in OutlinerTree to avoid discrepancies.
✅ Deploy Preview for heartex-docs canceled.
|
✅ Deploy Preview for label-studio-docs-new-theme canceled.
|
Refactored region index updates to a dedicated method `updateIndexes` for better consistency and maintainability. This ensures indexes are recalculated correctly after sorting, creation, or deletion of regions. Resolved a problem causing crashes due to observer side effects.
Gondragos
changed the title
LEAP-1709: Add region index displaying to relations list
feat: LEAP-1709: Add region index displaying to relations list
Jan 23, 2025
Gondragos
force-pushed
the
fb-leap-1709/region-index-in-relations
branch
from
January 23, 2025 07:10
e73d107
to
66e8b69
Compare
Added new utility methods for handling regions, labels, and localStorage in LSF helpers. Introduced customizable callbacks for `init` and improved functionality for ordering and deleting regions in the Sidebar.
Replaced `setRegionIndex` logic with a computed `region_index` derived from a new `regionIndexMap`. Add some new triggers for updateAppearenceFromState.
Gondragos
force-pushed
the
fb-leap-1709/region-index-in-relations
branch
from
January 23, 2025 16:28
66e8b69
to
1a87c42
Compare
Removed redundant updateIndexes calls and adjusted region_index getter to handle non-real regions properly. This improves performance and prevents errors related to invalid indexing.
Ensure localStorage values are correctly serialized only when necessary. This prevents potential issues when dealing with string data types.
Add integration test to verify region list consistency when regions are deleted or created. This includes handling changes affecting the entire list and ensuring correct relabeling and ordering.
/git merge develop
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR fulfills these requirements
[fix|feat|ci|chore|doc]: TICKET-ID: Short description of change made
ex.fix: DEV-XXXX: Removed inconsistent code usage causing intermittent errors
Change has impacts in these area(s)
(check all that apply)
Describe the reason for change
What is the new behavior?
Does this PR introduce a breaking change?
(check only one)
What level of testing was included in the change?
(check all that apply)
Which logical domain(s) does this change affect?
Relations Panel
,region_index