Refactor references to willTransition (#1731)#1734
Refactor references to willTransition (#1731)#1734mansona merged 3 commits intoember-learn:masterfrom
Conversation
|
👋 Replacing Maybe it's a good idea to reuse that example here as well?
The I think some of the copy around the code examples needs updating as well. For instance:
Could be updated to something like:
Could be that some of the other copy needs a bit of updating as well. |
|
Hi, thanks for your PR! I will review it this week. If anyone else has time to review sooner, please go for it. I need a little time to test the example in an app. |
jenweber
left a comment
There was a problem hiding this comment.
This is important prep for 4.0. Thank you!
| When a transition is attempted, whether via `<LinkTo />`, `transitionTo`, | ||
| or a URL change, a `willTransition` action is fired on the currently | ||
| active routes. This gives each active route, starting with the leaf-most | ||
| or a URL change, a `routeWillChange` event is fired on the [RouterService](https://api.emberjs.com/ember/release/classes/RouterService/events). This gives each active route, starting with the leaf-most |
There was a problem hiding this comment.
| or a URL change, a `routeWillChange` event is fired on the [RouterService](https://api.emberjs.com/ember/release/classes/RouterService/events). This gives each active route, starting with the leaf-most | |
| or a URL change, a `routeWillChange` event is fired on the [`RouterService`](https://api.emberjs.com/ember/release/classes/RouterService/events). This gives each active route, starting with the leaf-most |
This change is to make the linter happy.
c3d814e to
d5b3b2f
Compare
|
Percy is failing for some strange reason 🙈 I know what the issue is: the problem is that we have changed the browser since our last build on master 🙃 After we merge this the master will build again, and future PRs will be happy 🎉 |
Closes #1731
Remove references to deprecated
willTransitionand addrouteWillChange@jenweber Please review