-
-
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.isActive is undefined in Ember 2.8 #14268
Comments
Seems like a regression to me. |
Looks like tildeio/router.js@1db19a4 added The fix is to remove |
Should be fixed by tildeio/router.js#192 once it lands and is updated here. |
Thanks @rwjblue - I really appreciate your quick turnaround on this! 🍻 |
Testing my LTS app against the current pre-LTS Ember 2.8 version, I noticed that some of my routes started breaking because I was checking
transition.isActive
in route hooks.For instance, consider this block in a mixin to block mobile devices from accessing certain routes:
In Ember 2.4.x LTS
transition.isActive
is defined to be a boolean. In Ember 2.8.0,transition.isActive
isundefined
.To be honest, I can't remember why we were originally checking this, as it is an app that has been upgraded from early 1.x days. I also realize that this is likely caused by a router.js change, not something directly handled by Ember.
I think it will be safe for us to remove our check for that flag, but I wanted to call it out to make sure it's not an unintended change.
The text was updated successfully, but these errors were encountered: