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
Now if I click on the small x to reset the column filter to the default, I'd like to be able to see the null columns again. But instead the filter is reset to the configured min/max values and the rows with unset scores are still filtered out.
I'd like the [search][value] to become empty again here but I see no way to configure this and I admit I don't understand what's happening in the code in rangeNumberSliderClear as opposed to addRangeNumberFilter and/or addRangeNumberAndSliderFilterCapability.
The text was updated successfully, but these errors were encountered:
Not sure if this is a bug or a feature request.
(Test page: Sorry, not a public project. I'd have to see if I can come up with a minimal example if you can't reproduce this.)
I have a django application which filters float ranges for values that can also be null.
The yadcf initialisation options look like this for the respective column:
Before I touch the sliders, the rows null values are displayed in the datatable.
Corresponding part of query looks like this:
especially
[search][value]
is empty.As soon as I select either a min or max range, the unset values disappear, which is ok (because I want to have the proper range).
Corresponding part of query looks like this:
Now if I click on the small
x
to reset the column filter to the default, I'd like to be able to see the null columns again. But instead the filter is reset to the configured min/max values and the rows with unset scores are still filtered out.Corresponding part of query looks like this
I'd like the
[search][value]
to become empty again here but I see no way to configure this and I admit I don't understand what's happening in the code inrangeNumberSliderClear
as opposed toaddRangeNumberFilter
and/oraddRangeNumberAndSliderFilterCapability
.The text was updated successfully, but these errors were encountered: