feat(clearRefinements): support multiple indices

[francoischalifour]

Description

This implements multi-index context in ClearRefinements leveraging scopedResults (#3964).

A ClearRefinements widget now clears the refinements coming from its siblings and its children.

Implementation

init hook is now a noop

Since we now rely on the scopedResults given during render, init is a noop:

• It considers there are no refinements
• refine is a noop at this step
• createURL is a noop at this step

This is the reason why some tests have change from hasRefinements: true to hasRefinements: false at init.

Attributes were not deduped

This didn't cause any issues for the usage of the connector but I still dedup them in the new implementation to avoid inconsistent state if we're to build on top on this feature.

In the story, if you select "Samsung", "Apple", and "Cell Phones", the result is:

// Old implementation
['brand', brand', 'categories']  // Length: 3 => hasRefinements === true
// New implementation
['brand', 'categories] // Length: 2 => hasRefinements === true

This is using uniq which is not very costly for the number of attributes that we need to dedup.

Example

search.addWidgets([
  instantsearch.widgets.clearRefinements({
    container,
  }),

  instantsearch.widgets
    .index({
      indexName: 'instant_search_price_asc',
    })
    .addWidgets([
      instantsearch.widgets.refinementList({
        container,
        attribute: 'brand',
      }),
    ]),

  instantsearch.widgets
    .index({
      indexName: 'instant_search_rating_asc',
    })
    .addWidgets([
      instantsearch.widgets.refinementList({
        container,
        attribute: 'categories',
      }),
    ]),
]);

Preview

See stories →

[samouss]

Could you rebase? The history is a bit weird.

[francoischalifour]

I think @Haroenv played around for Netlify to report the deployments. It should be fine now.