You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Auxiliary routes can be targeted via the url, not via a router-link #4694
The auxiliary routing example (in the test code) navigates to the view with an auxiliary routing via the url. As far I can see, there does not seem to be a way to navigate to such a view using a router-link (from looking at the source code). Maybe this is on purpose, but we are left guessing how to use this feature, see also #4693.
changed the title [-]Auxiliary routes can be targeted via the url, not via a route-link[/-][+]Auxiliary routes can be targeted via the url, not via a router-link[/+]on Oct 13, 2015
Activity
[-]Auxiliary routes can be targeted via the url, not via a route-link[/-][+]Auxiliary routes can be targeted via the url, not via a router-link[/+]btford commentedon Nov 2, 2015
This is what I'm currently working on.
refactor(router): improve recognition and generation pipeline
refactor(router): improve recognition and generation pipeline
refactor(router): improve recognition and generation pipeline
refactor(router): improve recognition and generation pipeline
angular-automatic-lock-bot commentedon Sep 7, 2019
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.