Router's navigate() throws exception for component has no route config (in Alpha 38)

Just tried alpha 38 … found a few minor things, but this one is confusing on the router. We can now use navigate or navigateByUrl/ The latter accepts a string (the old style) and works. The former accepts a tuple, and tosses an error at me.

  // this works
  this._router.navigateByUrl(`detail/${this.selectedHero.id}`);

  // this does not work
  this._router.navigate([`./${Routes.detail.as}`, {id: this.selectedHero.id}]);

The error is ORIGINAL EXCEPTION: Component "HeroesComponent" has no route config.

See example here

https://github.com/johnpapa/angular2-tour-of-heroes/blob/master/src/app/heroes.component.ts#L38-L39

cc/ @btford:

[btford]

Yes– / means relative to the root of the application, and ./ means a child of this component.

So this is expected behavior, but the exception here could be a bit better.

[angular-automatic-lock-bot[bot]]

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}