numericfilters generates an error
See original GitHub issue× Error [Numeric filters] Can’t switch from the advanced to the managed API. It is probably an error, if this is really what you want, you have to first clear the numeric filters.
numericFilters: ['popularity > 2000'],
🔍 https://codesandbox.io/s/instantsearchjs-app-forked-4ob6g?file=/src/app.js:320-358
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
64230 - A "Must be a numeric value" error occurs when ...
System Reported Fixed* Reported Fixed*
Microsoft® Windows® for x64 3.71 5.2 9.4 TS1M5 Viya
Microsoft Windows 8 Enterprise 32‑bit 3.71 9.4 TS1M5
Microsoft Windows 8 Enterprise...
Read more >numericFilters API parameter - Algolia
Filter on numeric attributes. In most cases, use the filters parameter instead of numericFilters since filters has a more straightforward, SQL- ...
Read more >API proposal : advanced numeric filters · Issue #183 - GitHub
Error: [Numeric filters] Can't switch from the managed API to the advanced. It is probably an error, if this is really what you...
Read more >Illegal string offset 'value' in Drupal\views\Plugin\views\filter ...
Steps to reproduce * Create. ... You will get an an AJAX error, and the dialog box that pops up won't close, so...
Read more >Adding numeric filters - Amazon QuickSight
You create filters on numeric fields by specifying a comparison type, for example Greater than or Between, and a comparison value or values...
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
What’s happening is that the range component you are using actually behind the scenes uses both numeric refinements (not as a string, but as an object, which is what the original warning you got is about) and disjunctive refinements. To avoid you having to learn about those implementation details, we have added the ui state that maps more directly between the widgets and their state rather than search parameters (which could change in a minor version).
Hope that’s clear @dianos !
yes thanks; I found a different way to accomplish this as well using disjunctiveFacetsRefinements: { }, inside configure(). but still curious about ‘numericfilters’ not working. are you dropping support in favor of ‘filters’ ?