-
Notifications
You must be signed in to change notification settings - Fork 554
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
SPA problem #2 #654
Comments
One thing you can do is store the route to go back to in |
Can you tell me please what to do when I pass state. lock.on('authenticated', function (authResult) { It’s not working. I managed to have it work with: lock.on('authenticated', function (authResult) { But then it goes to home page and then to page on state and it’s not looking nice Thanks a lot |
Can you tell me please what to do when I pass state. If I do something like: lock.on('authenticated', function (authResult) {
}); It’s not working. I managed to have it work with: lock.on('authenticated', function (authResult) {
}); But then it goes to home page and then to page on state and it’s not looking nice Thanks a lot From: Ryan Chenkie [mailto:notifications@github.com] One thing you can do is store the route to go back to in params.state so that you can send the user back there after authentication. See this issue for more: #655 #655 — |
Can you tell me please what to do when I pass state. If I do something like: lock.on('authenticated', function (authResult) {
}); It’s not working. I managed to have it work with: lock.on('authenticated', function (authResult) {
}); But then it goes to home page and then to page on state and it’s not looking nice Thanks a lot From: Cristian Douce [mailto:notifications@github.com] — |
after login you get back to default route, not to one you were previously on
The text was updated successfully, but these errors were encountered: