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
Often, we need more than one class when we annotate image. There can also be some group of labels that have a meaning.
For example, let's take the example of the plane image :
The plane can be white/red, Boeing/Airbus.
It can have only one color and only one manufacturer.
What does this fix?
With this fix, we are able to group labels in subgroups.
In this case, we will group labels in combo-boxes.
What is the new behavior?
The UI will automatically group labels in subgroup.
If we activate mode "multiple" :
If we activate mode "subgroup":
labelstudio_car_example.mp4
What is the current behavior?
It will unpack all options and it will be complicate to identify main and subgroups.
What libraries were added/updated?
None
Does this change affect performance?
No
Does this change affect security?
No
What alternative approaches were there?
It would have been possible to create a complex taxonomy but it's much more impactful.
What feature flags were used to cover this change?
???
Does this PR introduce a breaking change?
(check only one)
For me it's not a major change because the old behavior is not impacted.
What level of testing was included in the change?
(check all that apply)
Which logical domain(s) does this change affect?
It will allow to annotate more precisely when we have "nested" classes on an object.