[question] Rationale behind $router.navigate

[cexbrayat]

I was wondering what the reasons are behind using a URL parameter in $router.navigate instead of a component name ?

To replace $location.path('/register'), I would have expect to write (maybe wrongly) :

$router.navigate('register');

instead of

$router.navigate('/register');

I was a bit surprised, as ng-link is working with component names.

To avoid remembering the URL, it's possible to do :

var url = $router.generate('register');
$router.navigate(url);

But that feels overkill... Am I missing something ? Or what are the reasons to use a url instead of a component name ?

[corbanbrook]

I agree, also using the component names would make it work like $state.go in ui-router as well.

[notrab]

👍

[Simon-Li]

+1 expect answers as well.

[ocombes-oss]

+1