François Chalifour

The `ais-configure` component is by default stripped out of the URL on purpose, you might want to follow the [routing guide](https://www.algolia.com/doc/guides/building-search-ui/going-further/routing-urls/angular/#seo-friendly-urls) to learn how to include it.

Thanks for the bug report. The issue likely comes from the [HitsPerPage](https://github.com/algolia/vue-instantsearch/blob/2a21b5226908f1f71c9ac28372de56d01eda813d/src/components/HitsPerPage.vue#L16-L21) component that doesn't pre-select the current refinement, as opposed to the [SortBy](https://github.com/algolia/vue-instantsearch/blob/2a21b5226908f1f71c9ac28372de56d01eda813d/src/components/SortBy.vue#L21) component.

Yes, it would be!

Not sure what you want to do, but you can add as many virtual `RefinementList` components as necessary in your tree—each with an attribute.

InstantSearch's geo search implementation only loads the results within the provided bounds. Here are more resources: - [Example](https://instantsearchjs.netlify.com/examples/tourism/) - [Example code](https://github.com/algolia/instantsearch.js/tree/b331cef9d8bc8683dd988daf40c5dc077f708548/examples/tourism) - [Guide](https://www.algolia.com/doc/guides/building-search-ui/resources/ui-and-ux-patterns/in-depth/geo-search/js/?language=javascript) - [API reference](https://www.algolia.com/doc/api-reference/widgets/geo-search/js/)

The [joepagan/vue-algolia-test](https://github.com/joepagan/vue-algolia-test) repo doesn't seem too representative of your issue, or is it? When a widget is mounted, it triggers a new network request. Could it be that in your...

In that case I would wrap `transformItems` in a `useCallback()` with the language as dependency. It would keep the `initialUiState` value across renders, and rerender when the language changes. I...

As @Haroenv mentioned, the reason why it can't work OOTB right now is because a prop change removes the widget, and then adds it back. The underlying InstantSearch.js library doesn't...

We don't yet provide a Hook to retrieve the loading state, but you can implement it based on the `results` returned by `useInfiniteHits()`. ```jsx import React, { useEffect, useState }...

@Haroenv `isSearchStalled` gets notified of the stalled status (not the loading status) after 200ms, so the button won't get disabled early enough. (You can decrease it with [`stalledSearchDelay`](https://www.algolia.com/doc/api-reference/widgets/instantsearch/react-hooks/#widget-param-stalledsearchdelay) but I...