New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add functionality to dispatch Route without change real URL #72
Comments
The usual way to do this on the web is to redirect to |
Interesting use case. I think I agree, the sign in step is a workflow within the secret app state. I wonder if this is the routers job, or if I should just have a signin component that "secret" uses and my signin route uses it too. Sent from my iPhone
|
I agree with @spicyj. The URL should dictate the UI that's on the page, namely Router.transitionTo(this.props.query.continue || 'home'); |
I think my comments were ambiguous.
|
I suppose you're right. I've investigated some of client and server side frameworks and found that it should not be concern of routing to replace one response with another. I'd like to close this issue. |
It would be nice to have functionality (in transition and Router itself) to dispatch specific route without change real URL.
E.g. I have auth flow close to https://github.com/rpflorence/react-nested-router/tree/master/examples/auth-flow . I visit my auth-only page
/secret
. Then I must be redirected to my auth page and URL in my address bar is/auth/signin
. But it would be better for user still see/secret
as URL and have some auth Route asactiveRoute
. In such case if I press Refresh I still have/secret
URL and can return to it after sign in. Now I have/auth/signin
and can't it.I see it as something like
The text was updated successfully, but these errors were encountered: