-
-
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 with dynamic segments throws error #10972
Comments
I think this is related to my issue #10945. I'd bet |
Yes, that is it. Setting the author queryParams as refreshModel: false workarounds the issue. Thank you @workmanw |
@novtor I checked in canary and my issues is still not working :( Here is an updated JSBin with Canary links. EDIT: Here is a permant (non-annoymous) JSBin link: http://output.jsbin.com/humibo/1#/post/1/comments?search=awesome |
You are right @workmanw , the bug persists, I was checking it on a route with refreshModel: false queryParams that's why it worked. |
In my case I was trying to retry an aborted transition, with identical results. Still not working with Ember 1.13.11. My workaround for this has been:
|
@LexLythius could you give me a better example of your workaround? I ran into this error when calling |
@erichonkanen Simply, you have to build the target URL manually -- with all complexities involved. E.g.: this.transitionTo("//yourdomain.com/#/some/path?query1=someValue&query2=another"); Useful pieces here are:
|
@LexLythius ok awesome ill try that thanks! |
Fix for #10945 was included in 2.4.4. This should have also been fixed. |
When retrying a transition with dynamic segments an error is thrown:
You didn't provide enough string/numeric parameters to satisfy all of the dynamic segments for route
My scenario:
And then reloads the entire page (with F5)
If user does only the first step and reloads the page, everything works fine
The text was updated successfully, but these errors were encountered: