Allow defining maxFacetHits independently from showMoreLimit in refinementLists that are searchable

[yonguelink]

A refinementList that is searchable and has showMore: true & showMoreLimit set to > 100 & you have clicked the Show more button, the search box does not work. That's because the maxFacetHits is limited to 100 for performance reasons.

Steps to reproduce the behavior

1. Go to https://codesandbox.io/s/infallible-aryabhata-l1w8x
2. Open your browser console (not the one in codesandbox)
3. Click on Show more
4. Type anything in the search box
5. See an error in the console

{
  debugData: [{…}]
  message: "Value too large for \"maxFacetHits\" parameter, expected integer between 1 and 100"
  name: "AlgoliaSearchError"
  statusCode: 400
  stack: "AlgoliaSearchError: Value too large for \"maxFacetHits\" parameter, expected integer between 1 and 100↵    at c (https://cdn.jsdelivr.net/algoliasearch/3.32.0/algoliasearchLite.min.js:2:21121)↵    at async Promise.all (index 0)"
}

Live reproduction:

https://codesandbox.io/s/infallible-aryabhata-l1w8x

🖥 Screenshots

Feature suggestion

I think it'd be a good option to be able to define maxFacetHits independently from the showMoreLimit in refinement lists. That way we'd be able to show however many values in one when no search is applied and still respect the API for maxFacetHits.

[Haroenv]

It may make sense to limit https://github.com/algolia/instantsearch.js/blob/master/src/connectors/refinement-list/connectRefinementList.js#L252 to 100 automatically so no error gets displayed, so that would become:

helper
  .searchForFacetValues(attribute, query, Math.max(getLimit(isShowingMore), 100), tags)

We probably want to add a warning in dev only as well when getLimit(isShowingMore) > 100

Would you be willing to make a pull request limiting the maxFacetHits?

In the mean time what you would be able to do (not so ideal, but possible) is create a custom search client (docs) and transform the parameter maxFacetHits to be maximum 100

What do you think?

[yonguelink]

This seems like a decent work around. It would avoid crashing and not returning anything.

For the problem we hit, we simply reduced our showMoreLimit to 100.

I'll check if I can make a PR without too much trouble.