Closed ZakKa89 closed 1 year ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Is this issue still important to you? If so, please leave a comment and let us know. As always, thank you for your contributions.
Nah don't close this please
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Is this issue still important to you? If so, please leave a comment and let us know. As always, thank you for your contributions.
Nah don't close this please
@ZakKa89 have you tried setting item_status as a disjunctive facet?
https://docs.elastic.co/search-ui/api/react/components/facet#example-of-an-or-based-facet-filter
@llermaly yes it actually already is a disjunctive facet.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Is this issue still important to you? If so, please leave a comment and let us know. As always, thank you for your contributions.
Nah don't close this please
Currently you can use setFilter to programmatically select a filter value like so:
I'm using that as a workaround to 'pre-select' certain values in the filter's UI.
However, if you want to do multiple, it doesn't work and only sets the last one:
So in above use case, MAINSTREAM will not be selected but SPARE-PART will.
Not sure if a bug, a feature that doesn't exist or if I'm doing something wrong? But the feature I'd want is to be able to pre-select certain filters in the config, but still be able to change these afterward.
But why not use the filter in the config?
Well, that filter technically works but doesn't update the UI at all. So it's not visible to the user... It's also a 'global' filter so it stays active. I tried to make sure:
That config will apply the filters but the values in the Facet will not be checked.