[Bug]: Spurious rerender at the start of a load about react-router HOT 4 CLOSED

Loader data is not compared for strict equality because we don't know the full structure of the data. It's often times something coming from an external data source (an API or database) that may have changed outside of the application and cannot be assumed to be the same.

You are also technically creating a new object every time you call return { results: "Hello World" }, so that wouldn't be strictly equal (i.e., { results: "Hello World" } !== { results: "Hello World" })

As a result of this, when you submit the form, we are re-running the loader and returning the data as a new instance back to the component. This happens any time the loader is re-run. It's very common for a <Form> action to modify the contents of the loader data, so we have re-run it to ensure it's in sync with anything external.

from react-router.

Hey @timdorr , thanks for your answer ! I think there's a misunderstanding.
I'm totally fine with 1 render, as I understand the constraints we're dealing with. However I see not 1 but 2 renders when clicking on the button: 1 right away, 1 after the loader runs. You can add a timeout to the loader or add more logs to check this further.
It would be good to reopen the bug, please :-)

from react-router.

#11134 (comment)

from react-router.

yes, I understand this is expected due to how things work internally, but I don't understand why this would be expected from the library user point of view.
I haven't worked much with contexts in the past, maybe the "state" and the "data" should be in 2 different contexts rather than the same one?
Thanks for your consideration.

from react-router.