-
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dynamic filter_spec: no variable selected should mean no filtering, and not filter out all data #32
Comments
If we want it to behave like e.g. Excel filtering, then no values should mean no rows selected. Provenance:
|
Also, we should keep it consistent with the factor filtering we have. I think if we have factors that behave differently than numerics it will be a mess because there is no visual indication of a filter being a factor or numeric. Provenance:
|
NEST/teal.devel/pull/721). In there, both factor and numeric behave the same way - no values selected, all rows filtered out. Provenance:
|
So then, no column selected should indicate no filtering? Currently, it is not possible to indicate no filtering whenever a filter_spec is provided. Provenance:
|
Conflict scenario: When filter_spec is not dynamic, how should it behave when all values (and therefore columns) are deselected? Provenance:
|
I think there are much more cases in here because we can consider whether a select spec is provided as well. Here is a link with a matrix of cases we can consider. https://drive.google.com/file/d/1lhgUqhTF3Jc_ethFALY74KZi3F90o5Ro/view?usp=sharing Right now, I am not sure what would make sense. I will be filling the matrix in as I figure it out. Feel free to jump in at the work @junlue I am not married to any ideas. Provenance:
|
BTW: I think the case when values are empty should always behave as filtering out all rows. Provenance:
|
NEST/teal.devel/issues/716
currently:
Despite
SEX
being selected in theselect_spec
there is no faceting becausefilter_spec
is not selected. Currently, iffilter_spec
is not selected then it filters out all data.At the very least, I think that if the variable of the
filter_spec
is not selected, then it should behave as if thefilter_spec
was simply not provided, i.e. no filtering.We should ask, are there cases where the user would want to filter out ALL data?
If not, then even in the case where the variable is not empty but the value is empty, it should also mean no filtering, and not filter out all like it does currently:
Provenance:
The text was updated successfully, but these errors were encountered: