Open FlorianJacta opened 2 weeks ago
this is really use-case specific
This is really specific but it happened for two clients already.
I think the "All" value is not generic and is extremely useful.
In terms of UX, I would use something like GitHub. Instead of having a specific "All" entry acting like an exception and potentially conflicting with an actual "All" value, I would add an icon/button to remove all filters. Just like the following screenshot:
I agree; the "All" value is here because I have to create a workaround. The firsr client wanted a behavior similar to Excel. I don't think we have to copy exactly what Excel has done because their drop-down selectors changes depending on the table and the filters
Description
I have an example coming from a real life use case from a customer about filtering a table.
The behavior is as followed (very similar to the Excel behavior for filters):
Solution Proposed
Here is the code created for this demo. The goal is to simplify this code and make this behavior or part of it inside Taipy directly.
Acceptance Criteria
Code of Conduct