-
-
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
Aborting a transition clears the resolved model #14721
Comments
@locks is it possible that the model is not kept on the application route since setup controller was never reached? Also I changed the Ember version to 2.9 and the last two LTS releases 2.8, 2.4 (I think) and the behavior was the same. |
@pixelhandler No, that's not the case. You can test this easily but writing an empty |
Any ideas on how to work around this? |
@btecu do you still have this issue, or did you find a work around? |
@pixelhandler still have the issue. See #16716. |
Noted that his has a PR for the test, #16716 |
I talked to @rwjblue about this in person and to add a bit more context, in the application model I load some meta data that is only ever going to be loaded once for the lifetime of the application. The issue appears when a user is loading say Somehow this causes the
|
@btecu glad you found a work around :) |
When you abort a transition in
afterModel
and go to an intermediate route, the model for the previous route does not exist, although it was resolved.https://ember-twiddle.com/db66247a084b6028d31c29ef856d7301 (See the console log)
The text was updated successfully, but these errors were encountered: