You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The filter implementation is a complete mess, so this may be hard to fix without a major code change.
The observation is, that every default filter is using string inclusion. And that's also true for selection filters, but it's obviously just wrong.
For example lets say you have a column that displays the two states "Available" and "Unavailable". Then the selection filter for "Available" will not filter anything, because "Available" is a case-insensitive substring of "Unavailable".
I never stop being suprised about how "smart" this table is.
The text was updated successfully, but these errors were encountered:
The filter implementation is a complete mess, so this may be hard to fix without a major code change.
The observation is, that every default filter is using string inclusion. And that's also true for selection filters, but it's obviously just wrong.
For example lets say you have a column that displays the two states "Available" and "Unavailable". Then the selection filter for "Available" will not filter anything, because "Available" is a case-insensitive substring of "Unavailable".
I never stop being suprised about how "smart" this table is.
The text was updated successfully, but these errors were encountered: