useRouter not updating state without useResponse about curi

[pshrmn]

This is the expected behavior.

React has an internal optimization that skips re-rendering an element if its props are the same as the previous render and its context has not changed.

My assumption is that you are rendering your App like this:

ReactDOM.render((
  <Router>
    <App />
  </Router>
), root);

in which case the App has no props, so the App will only re-render when the context has changed.

Curi uses two context providers: a router provider for accessing the router and a response provider for accessing the response/navigation objects. These are kept separately so that components that only need to access the router, like a Link, aren't forced to re-render when there is a new response.

When there is a new response, the response context is updated, so any component that accesses it (e.g. one that uses useResponse) will be re-rendered.

useRouter doesn't have the same effect; when there is a new response, the router context is still the same router object.

Does this make sense? I can update the documentation if it wasn't very clear on this.

[karandwivedi42]

Thanks!

I was actually using useRouter for router.current().response.name which I changed to useResponse and response.name.