Skip to content

Ability to find out where router navigation came from #45685

Closed
Closed
Ability to find out where router navigation came from#45685
Labels
area: routerdesign complexity: low-hangingeffort1: hoursfeatureLabel used to distinguish feature request from other issuesfeature: under considerationFeature request for which voting has completed and the request is now under consideration
Milestone
Backlog
@ychaikin

Description

@ychaikin
ychaikin
opened on Apr 19, 2022

Which @angular/* package(s) are relevant/related to the feature request?

router

Description

The angular router lacks what the "referer" header does in HTTP, so to speak.

Proposed solution

Create previousRoute as part of the API.

Alternatives considered

None.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: routerdesign complexity: low-hangingeffort1: hoursfeatureLabel used to distinguish feature request from other issuesfeature: under considerationFeature request for which voting has completed and the request is now under consideration

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions