Dhaya
Dhaya
Closing it, the current behavior works as intended and there are no changes planned for now.
Closing this issue. As mentioned, results are queried from within the provided bounds, which should prioritize retrieving documents to be used in a chosen marker clustering implementation.
Hi @pixelastic , do you think this issue is still relevant? The only thing we changed since then are that we can now customize CSS classnames and the InstantSearch.css package...
Hi! We're doing a round of clean up in this repository. This issue seems not to have generated much activity lately. Is it still relevant?
This should be working as expected starting from [email protected] which deprecated string-based templates and introduced tagged templates with [htm](https://github.com/developit/htm).
Closing this issue. For the latest version of InstantSearch.js, hiding the average with CSS still works, and it seems impossible to set the min/max values to the same value with...
This should be now handled thanks to https://github.com/algolia/instantsearch.js/pull/5045.
Got it, thanks!
Hi! We're doing a round of clean up in this repository. Is this still an issue for you or does the workaround works well enough?
Closing this issue in favor of https://github.com/algolia/instantsearch.js/discussions/5098 which has more activity.