-
Couldn't load subscription status.
- Fork 3.1k
fix: OPTIC-1341: Filtering on data fields is not working when $undefined$ and other columns in task data #6641
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
…ned$ and other columns in task data
✅ Deploy Preview for heartex-docs canceled.
|
✅ Deploy Preview for label-studio-docs-new-theme canceled.
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #6641 +/- ##
===========================================
+ Coverage 76.67% 76.70% +0.02%
===========================================
Files 169 169
Lines 13844 13853 +9
===========================================
+ Hits 10615 10626 +11
+ Misses 3229 3227 -2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
…ned$ and other columns in task data (HumanSignal#6641)
Change has impacts in these area(s)
(check all that apply)
Problem
Data manager filtering does not work for columns different from those in the label config when$undefined$ is in the task data.
Steps to reproduce
Import 2 files (e.g. image) without settings labeling config. You will get 2 tasks.
Patch the first task only with new fields, e.g. add some_value: "my-data" column.
Try using filters by some_value in the data manager, you will see “not found” even if you try to search for “my-data”.
It happens, because the data manager engine forces to use$undefined$ column for search.