Which kinda makes sense doesnโt it. React aside, typical web based routing that serves different HTML pages based on the URL will definitely not retain your local state between routes unless you implement some sort of store or caching solution. The routing behavior of unmounting a component when the URL changes sort of fits into that narrative.
I am curious though, did you notice any performance difference between using the render prop VS the child node?
๐ Hi, Iโm @santiago correa
๐ Iโm interested in dominating the world.... Just kidding just want to make the web a better and accessible place for all.
For anyone curious, this is the documentation for the specific mounting behavior mentioned by the author : reactrouter.com/web/api/Route/rend...
Which kinda makes sense doesnโt it. React aside, typical web based routing that serves different HTML pages based on the URL will definitely not retain your local state between routes unless you implement some sort of store or caching solution. The routing behavior of unmounting a component when the URL changes sort of fits into that narrative.
I am curious though, did you notice any performance difference between using the
renderprop VS the child node?Edit: store or caching solution
Hi there,
No i didnโt really notice any performance improvements between using component and render