Skip to content

angular_1_router: double slash at the root when path is the root itself #7633

Closed

Description

@0cv

Regarding the new Angular1 Router (for 1.5), there is an issue when defining the root component with a path like path: '/...' or path: '...'. I have taken the sample application to illustrate the issue:
http://plnkr.co/edit/FVZZwxAjlOmxQ8uA9YLF?p=preview

Click on "Heroes", and then hover over the list. You will see paths like xxxxxx//10 instead of xxxxxx/10.

The only difference compared to the sample application is the line 20 in app.js.

Activity

  1. ericmartinezr commented on Mar 16, 2016

    @ericmartinezr
    Contributor

    This was supposed to be fixed in #6729 but I don't know if the fixes for ng2 router are valid for ng1 router too.

  2. btford commented on Mar 23, 2016

    @btford
    Contributor

    I think @petebacondarwin just solved a similar issue specific to Angular 1. I expect #6729 to have fixed this, but Pete would know better than I.

  3. itsmunim commented on May 18, 2016

    @itsmunim

    Is this going to be resolved some time soon? Or anyone going to give it a go? @btford

  4. petebacondarwin commented on May 18, 2016

    @petebacondarwin
    Contributor

    We are currently undergoing a review of the router design. This will significantly affect this router. I would wait for a week and there will be some more information about what will happen next.

  5. petebacondarwin commented on Jul 12, 2016

    @petebacondarwin
    Contributor

    So we have a new router, based a lot upon Observables. We are currently investigating how to backport this to Angular 1. Either way, the version of the router to which this issue refers is no longer maintained. So we will not be providing a fix.

  6. angular-automatic-lock-bot commented on Sep 9, 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.

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

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions