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
Erase the "less than" field manually (not using the dedicated button)
Result : all the rows are now filtered out.
The reason seems to be that the term value is not reset to null or undefined when the corresponding field is erased by hand, but is still taken into account because another filter on the same column still has a "valid" term value.
This behaviour is reproducible on the filtering tutorial :
Result : all the rows are now filtered out.
The reason seems to be that the
term
value is not reset tonull
orundefined
when the corresponding field is erased by hand, but is still taken into account because another filter on the same column still has a "valid"term
value.I managed to fix this by testing for an empty string when number values are involved, but I'm not sure at all whether this is a convenient solution, or if this could bring unwanted side-effects.
Please let me know what are your thoughts about it, and whether I can create a PR with the possible fix.
The text was updated successfully, but these errors were encountered: