instant-search
Here are 29 public repositories matching this topic...
-
Updated
Jun 16, 2020 - Swift
-
Updated
Nov 19, 2019 - Swift
-
Updated
Jul 1, 2019 - Kotlin
-
Updated
Jun 16, 2020 - Kotlin
Allowed:
filtersfacetFiltersnumericFiltersaroundLatLng(only ifaroundRadiusis present too)insideBoundingBoxinsidePolygon
Anything else should trigger an IllegalArgumentException.
-
Updated
Jun 15, 2020 - Kotlin
-
Updated
Jun 10, 2020 - Swift
-
Updated
May 25, 2019 - Shell
I ran through the tutorial and ( so far) have found some issues.
Here are my notes and my progress so far. Hope its useful
-
Updated
Jun 6, 2018 - Kotlin
-
Updated
Jun 12, 2020 - Python
As a follow up to a forum request regarding a conflict with another plugin, it would be nice if we could let users enable/disable the backend search from the settings page.
We need to ensure that it defaults to enabled for making a smooth transition for existing users.
Create a histogram style filter component. e.g. see price filtering component on Airbnb search results page. Component should include all the functionality from the AIrbnb version.
Component should allow the user to see the distribution of values of a particular field and allow them
-
Updated
Apr 18, 2019 - Java
-
Updated
Sep 5, 2018 - JavaScript
-
Updated
Jun 15, 2020 - JavaScript
-
Updated
Apr 26, 2020 - JavaScript
-
Updated
Mar 19, 2017 - JavaScript
-
Updated
Jun 7, 2020 - JavaScript
-
Updated
Feb 14, 2019 - Java
-
Updated
Jun 2, 2017 - JavaScript
-
Updated
Mar 6, 2018 - CSS
-
Updated
Dec 21, 2017 - Kotlin
-
Updated
Mar 24, 2018 - JavaScript
-
Updated
Jan 23, 2017 - Java
-
Updated
Apr 25, 2020
-
Updated
Sep 27, 2017 - JavaScript
-
Updated
Jul 9, 2018 - Java
Improve this page
Add a description, image, and links to the instant-search topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the instant-search topic, visit your repo's landing page and select "manage topics."

Bug🐞
I'm using the default example from the documentation.
What is the current behavior?
Visiting pages with Algolia components cause the memory to continue to grow up without stopping. After ~ 1000 urls (depends on how much HTML there is in page) the server is _out of mem