Allow passing transient `info` in navigations

[atom-git]

What problem is this solving

This would allow passing information specific to the navigation (https://github.com/WICG/navigation-api#example-using-info)

Proposed solution

TBD
This requires an RFC

[posva]

This is what we call transient state (state available only during navigation) and is planned in a way that would align with the upcoming navigation API (https://github.com/WICG/navigation-api#example-using-info). It would require going through an RFC first though

[jods4]

Big +1 for transient state!

• It has some useful applications (not the least being force reloading a component when the route doesn't change);
• and it's incredibly difficult to work around, the router code goes to great lengths to "normalize" everything passed in the route and only selectively copies properties.

There are few places where you could pass "hidden" state, most likely params, but in most cases only known keys will passthrough. I say "in most cases" because the code around this is relatively inconsistent. For example if you're modifying the current route and pass no name, params doesn't get normalized (for unclear reasons, seems pretty inconsistent).