Allow passing state to link/setLocation about wouter

[destructobeam]

Hey @molefrog,

Do you know the rationale is behind the intentional lack of support? I’m curious as to why that would be.

I think it’s a nice interface for passing animation names and vars between routes, and anything else you need to pass additional parameters to without gumming up the URL with params or necessitating a global state management lib. It also persists state changes across browser native back/forward buttons which is nice.

It makes sense to me to have it as part of the wouter lib as the history API methods are already utilised, so it would potentially be less overhead and a cleaner API than an isolated solution that would require wrapping each component? But I could be missing something here.

Cheers!

[molefrog]

@destructobeam Hi and thanks for the issue!

I see that this is something that we intentionally don't support in wouter, but since pushState supports it, why wouldn't we implement this? However, my concern is if it's actually going to be used by developers.

Can you provide a use case? Thanks!

[molefrog]

The discussion moved to #102