-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
transition.retry
broken w/ initial transition on Ember-2.14.0-beta.1
#15190
Comments
Ya, the bug is ultimately over in router.js. It seems like an interaction between tildeio/router.js#211 and tildeio/router.js#197. It may just be that if the initial transition is aborted, that we change the method from @cibernox / @alexspeller - Can one of y'all take a look and help me hash out the right solution? |
I'm on holidays until Wednesday. Since my change was the last one, I'd try the same reproduction with the previous version of router.js. At least we know what PR broke it, although I suspect it's mine. |
Ya, almost certainly yours. However, I think the solution is that we need to do the same sort of thing before deciding to inherit the method type. Basically, if the method type set to |
I'm staring at a deadline at the moment, I'll look at this ASAP |
I'll also try to look at this at some point today. |
transition.retry
broken w/ initial transition on Ember-2.13.0-beta.1transition.retry
broken w/ initial transition on Ember-2.14.0-beta.1
tildeio/router.js#213 should fix... |
Here is a reproduction app: https://github.com/workmanw/router-retry-bug
Here is a live demo: https://workmanw.github.io/router-retry-bug
(I couldn't make a twiddle because it doesn't seem to support beta builds at the moment)
The issue seems to be that if the initial [first] transition within an ember app is aborted via redirect, then later someone tries to call
transition.retry
it doesn't work as expected. While it does ultimately transition correctly, it doesn't update the URL. You should be able to easily reproduce this with the live demo above.I bisected this issue and it seems to be cause by this PR: #15168
CC: @cibernox
The text was updated successfully, but these errors were encountered: