Correct order in which to set ui state and configuration

[callmekatootie]

I am trying to change multiple properties in ui state at the same time. Namely configure.{multiple properties} and refinementList.{multiple refinements}.

I find that using setIndexUiState() alone does not work - specifically for configure attributes... (I have a <Configure /> component too - meant to set initial values but I am not sure if that is playing a role in this issue). I also came across a similar open issue here.

Anyway - I was able to work around it by using both setIndexUiState() and refine() from useConfigure() - my question is, which one should come first? Should configure's refine() be called first and then setIndexUiState((prevUiState) => {}) be called first or configure's refine()?

[Haroenv]

Unfortunately I don't think this use case is entirely optimised, but set ui state is debounced, and refine of widgets isn't. Therefore this combination will always do multiple searches.

Configure works best if it's only controlled with props, have you tried that option (calling setUiState for refinement list, and changing the props of a configure)?

I think in general it may be best to create a sandbox so the timing constraints of your whole app can be taken in account.

Which parameter is it that you're changing at the same time?

[callmekatootie]

Yeah - I am doing exactly that right now, because I find that sometimes the configure does get set and sometimes it doesn't (probably a race condition with useConfigure and setIndexUiState both updating the state at the same time).

I am checking if using <Configure /> with the props will work better... I am changing the aroundLatLng and aroundRadius params...

[Haroenv]

I see, yes that's probably a race condition