Route state

[paratron]

Route state

[Paratron]

I am really not sure about this. My belly tells me that the state should be managed in React/Redux and not in the browser history. Googling how you would do this in React Router also shows some really messy solutions. Even the StackOverflow question about whats the purpose of state objects in browser history doesnt give good examples.

I fear implementing such a mechanism that closely tied to the most basic building blocks of hookrouter invites for misuse through users.

[danielkcz]

Sure, it's not like I am using it often, but sometimes it happens. It can be useful for some optimization to basically pass data that are available on the current page so the next page can render faster because it knows something sooner, eg. form layout.

The main difference is that such state is tied to that exact navigation intent. If you go back in history or even refresh a browser, that state is there. If it would be solved on an app state level, it's fairly risky to run into some unexpected behavior.

[danielkcz]

Ah, I see now why you do not want to implement it. It clashes with API of #1. Makes sense that query params are probably more common than route state. I will try to figure if I can live without it or eventually fork the lib.