Skip to content

Auxiliary routes can be targeted via the url, not via a router-link #4694

Closed

Description

@Krustie101

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.

Activity

  1. 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
  2. self-assigned this
    on Nov 2, 2015
  3. btford commented on Nov 2, 2015

    @btford
    Contributor

    This is what I'm currently working on.

  4. added 7 commits that reference this issue on Nov 20, 2015
    cf7292f
    9e3ab04
    520af55
    6ddfff5
  5. angular-automatic-lock-bot commented on Sep 7, 2019

    @angular-automatic-lock-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.

  6. locked and limited conversation to collaborators on Sep 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

effort1: hoursfeatureLabel used to distinguish feature request from other issues

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions