Closed FlorianJacta closed 2 months ago
I've fixed the problem But an issue remains: what's the behavior of the filter on multi-valued properties like tags right now, the only operator that works is "contains" and the tested value needs to equal one element of the set. What would be the ideal behavior ?
equals
never works? If so, it should be deleted from the filters list, and a not contain
should appear.
AND you can only test again a "full" tag
I think getting the tags lov to counter this problem should be great. It can be quite hard as it is interactive but that would be best
I think getting the tags lov to counter this problem should be great. It can be quite hard as it is interactive but that would be best
what do you mean?
If I add a new tag to a scenario, I should see it in the filter for tags. I should have a selector of tags inside the filter section instead of having a free text input.
During the discussion, we decided to propose the list of authorized tags from the configuration. We can evaluate the possibility to support a dynamic list of tags in another issue
we now support equals, not equals and contains (on each element of the tags list)
What went wrong? 🤔
Filtering on tags needs to be fixed. When a scenario has a tag, and the user filters it to get it, all the other scenarios disappear, which means this scenario is also filtered.
Expected Behavior
The filter should work correctly.
Steps to Reproduce Issue
Run the code and filter the scenarios with "Tags" contains or equals test.
Version of Taipy
Develop - 6/6/24
Code of Conduct