Jason Stoltzfus
Jason Stoltzfus
Hey @apellizzn Yes, "any", "all", and "none" would be the only valid values.
This: ```js { "states": ["California", "Alaska"] } ``` Is functionally equivalent to: ```js { "any": [ { "states": "California" }, { "states": "Alaska" } ] } ``` So if we...
The real world use case would be any Facet where you want to select multiple values to filter on that are all true. Like if you are trying to find...
Yes. On Tue, Oct 29, 2019, 8:39 AM Johan Arnör wrote: > Ah, now I see. That would require ammenity to be stored as an array I > suppose? >...
Noting here that this request was also made in https://github.com/elastic/search-ui/issues/411.
Hey! Would love to help you out, not sure how soon we can get to this, unfortunately.
I did the following to test this. Testing was performed in the "examples/sandbox" project. I added the following policy in a meta tag in `index.html`. ``` ``` And ran it...
Updating to react-select v3 will likely be a breaking change, as the markup and classnames will likely be differently. If we do this, I think we need to take the...
@yakhinvadim If you get a moment, could you see if this is solved after updating react select?
While "Hierarchical facets" aren't supported from a UI perspective, I want to call out that we do have "conditional facets" available, which in conjunction with flat facets (what we have...