@mtangoo In my opinion, I don’t see it should be necessary to think where I am when I am thinking in where I want to go, specially when both method implementations require the same input and the final result is the same.
I think you’re right — it’s a little weird. That being said, there is an RFC for a new Router Service that would replace both of those with a service that has it’s own hooks in whatever Ember Object you inject it into. So you’d do:
this.get('router').transitionTo('planet.mars');
It’s got a bunch of other nice little ideas too. Not sure whether it’s being actively developed or when we should expect something.
@Spencer_Price that has more sense, not only because the naming thing is more coherent but because there is a Module who is charge of the transitionthis.get('router') and not the Component where your code is: this .
It is taking me a lot of effort to understand the Ember philosophy, a very few things are intuitive for me… yet