Jason Stoltzfus
Jason Stoltzfus
Sorry for the delay. Are you using this with App Search? Or Elasticsearch? Or some other backend? I'm having trouble wrapping my head around your problem. I'm going to close...
That's a really good point. Being able to handle this scenario would be really valuable, especially given i18n requirements. I actually think it'd be easy enough to add support for...
Got it. For what it's worth, in the meantime, you *should* be able to create a "Custom" view for this. The process describing how to do this can be found...
@m-sureshraj Yes! I'm going to publish a PR very soon for performance issues that will relate to this. So just wait for that PR to merge to avoid conflicts.
@m-sureshraj https://github.com/elastic/search-ui/pull/249
@m-sureshraj No blockers, feel free to work on this. I suggest posting the proposed API for this here for discussion before you get too far along on this task, it...
@PRASHANT1104 That would be great.
"all" would be the default at the top level.
@abhishekKrHaith11 The first structure you showed would not be possible, but something functionally equivalent would be. ``` addFilter("states", "California", "all", "all") addFilter("world_heritage_site", "true", "all", "all") addFilter("acres", "40000", "all", "any") addFilter("square_km",...
The one thing unique about this, is there is logic that looks to see if a matching filter is already applied to that field, and if so, it adds the...