Gerard Sans
Jul 24, 2017 · 1 min read

Great! Glad to hear that! 😃

I see from where you are coming from. I know… It’s itchy having the two same strings in the route definition! But unfortunately, the path is not always a clean string that you can translate into a trigger state so I would not recommend that approach in general.

Besides that you can also pass configuration options to your transitions in the form of an object [@routerTransition]="{ value: 'home', params: { time: '100ms' } }" which would not be possible with your alternative.

    Gerard Sans

    Written by

    Developer Advocate @AWSCloud | Just be AWSome | MC Speaker Trainer Community Leader | Views are my own | @fullstackcon @ReactiveConf @ngcruise @UphillConf UK ☂