This repository has been archived by the owner on Jul 11, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 46
Avoid callback for outdated queries #29
Milestone
Comments
Do you mean we want to "cancel" cases like: helper.search() //slow one, cancel it
helper.search() // fast one, get it Would it be transparent for the user that he will only get results for second search? I guess if we are using an event emitter and the two requests were for the same search then it might not be a good idea to trigger it twice indeed. But what if the user did two different searches? |
The helper is not meant for doing "two different searches", the helper managed the state of the search : the whole state. If you are using 2 indexes, you probably should use two helper instances. Same for helpers based on two separates parts of a UI. |
Kinda related with #31 (see the proposed fixed) |
bobylito
pushed a commit
that referenced
this issue
Jun 15, 2015
* FIX : #29 Avoid callback for outdated queries * FIX : #64 Sum up the processing time of all queries * FIX : #92 Parameters that can be set in the dashboard shouldn't have defaults * FIX : #62 Make sure disctinct is set to false when it's not possible to use distinct in Algolia * FEATURE : #91 Support for tags (with support for the raw format #98) * FEATURE : #70 Ability to get all refined values : helper.getRefinements( facetname ) * FEATURE : #51 multiple filters for a single conjunctive facet (tests) * FEATURE : Ability to modify any parameter of the state easily (#76 #84 #12) * FEATURE : #69 Ability to know if a facet is refined, whatever the value * FEATURE : #86 Expose SearchParameters, AlgoliaSearchHelper, SearchResults to users directly in the builds * FEATURE : #25 let the user do a clearRefinement with a function as a filter * REFACTORING : SearchParameters is immutable (#14) * REFACTORING : Ensure SearchParameters is totally frozen (#14) * LIB : Update lodash version to 3.9.x
dhayab
pushed a commit
to algolia/instantsearch
that referenced
this issue
Jul 10, 2023
dhayab
pushed a commit
to algolia/instantsearch
that referenced
this issue
Jul 10, 2023
* FIX : algolia/algoliasearch-helper-js#29 Avoid callback for outdated queries * FIX : algolia/algoliasearch-helper-js#64 Sum up the processing time of all queries * FIX : algolia/algoliasearch-helper-js#92 Parameters that can be set in the dashboard shouldn't have defaults * FIX : algolia/algoliasearch-helper-js#62 Make sure disctinct is set to false when it's not possible to use distinct in Algolia * FEATURE : algolia/algoliasearch-helper-js#91 Support for tags (with support for the raw format #98) * FEATURE : algolia/algoliasearch-helper-js#70 Ability to get all refined values : helper.getRefinements( facetname ) * FEATURE : algolia/algoliasearch-helper-js#51 multiple filters for a single conjunctive facet (tests) * FEATURE : Ability to modify any parameter of the state easily (algolia/algoliasearch-helper-js#76 #84 #12) * FEATURE : algolia/algoliasearch-helper-js#69 Ability to know if a facet is refined, whatever the value * FEATURE : algolia/algoliasearch-helper-js#86 Expose SearchParameters, AlgoliaSearchHelper, SearchResults to users directly in the builds * FEATURE : algolia/algoliasearch-helper-js#25 let the user do a clearRefinement with a function as a filter * REFACTORING : SearchParameters is immutable (algolia/algoliasearch-helper-js#14) * REFACTORING : Ensure SearchParameters is totally frozen (algolia/algoliasearch-helper-js#14) * LIB : Update lodash version to 3.9.x
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Depending on the network, it may happen that a request sent before another is received after. This should not happen, and shouldn't be left to the responsibility of the user.
The text was updated successfully, but these errors were encountered: