This repository has been archived by the owner on Dec 30, 2022. It is now read-only.
connectAutocomplete can’t work if you’re in a single-index context #74
Assignees
Comments
Haroenv
added a commit
that referenced
this issue
Apr 30, 2017
Haroenv
added a commit
that referenced
this issue
Apr 30, 2017
mthuret
pushed a commit
that referenced
this issue
May 2, 2017
) * fix(connectAutoComplete): allow usage with hits from a single index fixes #74 * fix(connectAutoComplete): use single/multi index API * fix eslint
mthuret
pushed a commit
that referenced
this issue
May 2, 2017
<a name="4.0.0-beta.5"></a> # [4.0.0-beta.5](v4.0.0-beta.4...v4.0.0-beta.5) (2017-05-02) ### Bug Fixes * **connectAutoComplete:** allow usage with hits from a single index (#75) ([8b3b358](8b3b358)), closes [#74](#74) * **InstantSearch:** update algoliaClient when it change (#70) ([9e97dbd](9e97dbd))
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Do you want to request a feature or report a bug?
bug
Bug: What is the current behavior?
connectAutocompleteassumes that there are multiple indices, and this iterates over all of the keys to aggregate the hitsBug: What is the expected behavior?
it should only do that if we’re in a multi-index context
The text was updated successfully, but these errors were encountered: