feat(autocomplete): support global onSelect and redirect to search page

[dhayab]

Summary

This PR adds two top-level parameters to autocomplete:

• getSearchPageURL to provide an URL to navigate to when autocomplete is not part of the search page
• onSelect to provide a global onSelect, making the per-index one optional, and defaulted to a method that handles redirection to the search page if necessary

The order is the following:

1. if the index / suggestion index provides getURL() → navigate to url
2. if autocomplete is not part of the search page and getSearchPageURL() exists → navigate to url
3. refine using getQuery()

FX-3538

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit cf22472:

Sandbox	Source
example-instantsearch-getting-started	Configuration
example-react-instantsearch-getting-started	Configuration
example-react-instantsearch-next-app-dir-example	Configuration
example-react-instantsearch-next-routing-example	Configuration
example-vue-instantsearch-getting-started	Configuration

[dhayab]

I'll update the API reference, and will add tests after #6772 is merged.

[shaejaz]

lgtm, couple of minor comments.

[shaejaz]

Is there a possibility this can cause an indexing error?

[dhayab]

targetIndex is at least the mainIndex (the parent of the isolated index of an autocomplete), so it should not cause an error. It just is typed as potentially undefined because the renderState needs to be declared before we have access to instantSearchInstance.

[shaejaz]

Is it not possible to also get this info from the targetIndex in react?

[dhayab]

For now this is defined in the JS widget, and retrieving the index instance in React is not as easy (useIndexContext() is not publicly exported for instance).

Could be worth having it returned by the connector in a future update though.