fix(connectSortBy): do not throw with wrong indexes #3824
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
sortBy
connector used to throw an error when the current index wasn't listed in theitems
of the widget.This broke some users' apps when using
routing
. If users type a URL with a wrong index name for thesortBy
widget, it will throw straight away and break the InstantSearch lifecycle.This PR removes the error thrown and rathers warns only in development. The initial index (from the helper) is used if that happens.
I slightly changed the implementation because we were relying on the InstantSearch instance index (
instantSearch.indexName
) and now use the helper index (helper.getIndex()
). This shouldn't break anything and is more consistent within the connector.The deleted tests in the widget are now covered in the connector.