Youcef Mammar

Hi @stefanbuck, thanks for your interest in this use case. Here is an example where the NODE_PATH is used and OctoLinker isn't behaving as expected. 1. Go on https://github.com/skvale/react-postgraphile/blob/master/src/apollo-provider.js#L6 2....

I agree. Feel free to close the issue. Can we imagine providing a way to configure path resolution with OctoLinker? It could be a field injected on the page or...

Hi @bootsmann1995 usually when you want to add state from the server, you'd rely the routing feature, and so you'd be able to pass a state via the url like...

Hi @Wozniaxos thanks for providing the example but I wasn't able to get it to hang. Can you detail the steps to witness this behaviour?

So this can be closed?

For anyone stumbling on this issue: it's worth nothing that it's currently possible with a custom range-input widget (for both Vue InstantSearch and Angular InstantSearch) https://www.algolia.com/doc/api-reference/widgets/range-input/vue/#customize-the-ui.

Hi @Jefiozie. Thank you for reviving this topic. I'm new to angular myself and I may be missing your point. Can you please explain `Maybe we can create a service...

https://www.algolia.com/doc/guides/building-search-ui/going-further/routing-urls/angular/ And there's more about the that routing object on InstantSearch.JS documentation, which Angular InstantSearch is based upon. https://www.algolia.com/doc/guides/building-search-ui/going-further/routing-urls/js/?language=angular#references

Hi @Celtian sorry for the late reply. For now the easiest workaround is not to use `routing: true` but a custom router. ```ts ... import { history as browserHistoryRouter }...

Hi @louislebrault thanks for reaching out. Indeed it would be helpful to have a codesandbox, preferably simplified to narrow down the issue. It looks like the codesandbox we have on...