Support for "or" filters
See original GitHub issueI would like to search for results whose ID is 123 OR within specific distance, but now I can only get results when I search with ID 123 AND within specific distance. Can we have the OR filters feature in the future?
const config = {
trackUrlState: false,
initialState: {
filters: [
{
field: "id",
values: ["123"],
type: "any",
},
{
field: "location",
values: [{
center: "22.502022, 114.078639",
unit: "km",
to: 200,
from: 0,
}],
type: "any",
},
],
},
apiConnector: connector,
};
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
"filter" | Can I use... Support tables for HTML5, CSS3, etc
Method of applying filter effects using the filter property to elements, matching filters available in SVG. Filter functions include blur, brightness, ...
Read more >what is meant by support of a filter?
Therefore, the most strict definition of support is that it is the set of displacements where the kernel function is non-zero. This could...
Read more >Filter Support - Avanti Polar Lipids
610014 | Filter Support For use with the extruder to provide extra support and improved flow rate. It provides a flat surface to...
Read more >Support | Filters Fast®
Support at Filters Fast. Call 866 438 3458 (Toll Free), email support@filtersfast.com, or text 704 228 9166 to speak with a water or...
Read more >Search Filters - Support
Personal filters are personal attributes about who a program serves, such as age, gender identity, veteran status, health information, and more.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thank you all for sharing this concern. I’d considered this before but then incorrectly decided there wouldn’t be a need for it. I see now that was an incorrect assumption.
I believe there was a PR that was submitted previously that we ended up closing. Let me see what I can dig up.
I’m going to close this in favor of https://github.com/elastic/search-ui/issues/411, let’s continue the conversation there.