Childrouting inside auxiliary outlet works only in very specific cases #26672

Activity

1. pkozlowski-opensource

   added

   area: router

   on Oct 26, 2018
2. ngbot

   added this to the needsTriage milestone on Oct 26, 2018
3. jasonaden commented on Nov 27, 2018

   

   jasonaden

   on Nov 27, 2018

   Contributor

   More actions

   @luckylooke Can you please add some more detail? Such as what actions you want me to take when reproducing and what the expected result should be? It looks like you put together some good samples, but your steps to reproduce don't tell me anything useful and the general statement that "Routing inside auxiliary routes is broken" also doesn't help as it doesn't say how it's broken or what exactly you're running into.
4. luckylooke commented on Dec 6, 2018

   

   luckylooke

   on Dec 6, 2018

   Author

   More actions

   Yes I am really sorry I should review my question after some time to get 3rd person view on it :) Now I see how badly I wrote it, I did not left any context here or real steps.

   Situation:
   AppComponent ( root, have two outlets one unnamed and one named 'secondary' outlet )
   AuxComponent ( has one unnamed outlet )
   OneComponent, TwoComponent, ThreeComponent ( basic components, nothing special )
   All routes configuration is in app.routing.module.ts.

   Ok, so at first it loads in empty route state:
   OneComponent is loaded into root primary outlet and AuxComponent is loaded in secondary outlet. As AuxComponent have nested outlet with children routes defined in router config, redirection should be applied to go to 'three' route. This is not happening.

   Navigating to '/two' ([routerLink]="['two']"), pretty same scenario is expected in secondary outlet. Again no redirection happens.

   Navigating explicitly to '/(secondary:three)' ([routerLink]="['', {outlets:{secondary:['three']}}]") works.
   But navigating explicitly to '/two/(secondary:three)' ([routerLink]="['two', {outlets:{secondary:['three']}}]") does not, it throws error that it cannot match segment 'two'.

   Navigating from '/(secondary:three)' to '/two' keeps secondary outlet untouched (ThreeComponent displayed), url is changed to '/two(secondary:three)' as expected.

   But navigating from '/(secondary:three)' to '' or '/' removes navigation from secondary outlet. I am expecting same behaviour as for '/two' that secondary routing will be kept untouched.

   Probably it will be better after applying recent fix 20cef50 by Igor.

   Maybe also Maxim's #25483 could help.

   Thank you for your time! You are awesome! :)
5. benlesh

   added

   type: bugfix

   severity3: broken

   on Dec 13, 2018
6. petebacondarwin

   added

   type: bug/fix

   and removed

   type: bugfix

   on Dec 14, 2018
7. jasonaden commented on Dec 18, 2018

   

   jasonaden

   on Dec 18, 2018

   Contributor

   More actions

   Thanks for the update! We tried to merge the commit 20cef50 which was actually submitted by a community member.

   We had an issue internally that caused that commit to be reverted, but we will be looking at getting it merged again as soon as possible.

   I'll take a look at the additional info. Thanks!

   👍React with 👍3Reacted by Maxime, Steve Schwarz and Bryan
8. atscott

   added

   freq2: medium

   on Dec 5, 2019
9. ngbot

   modified the milestones: needsTriage, Backlog on Dec 5, 2019
10. atscott

    added

    router: aux routes

    router: URL parsing/generation

    state: confirmed

    triage #1

    on May 27, 2020
11. jelbourn

    added

    P3An issue that is relevant to core functions, but does not impede progress. Important, but not urgentAn issue that is relevant to core functions, but does not impede progress. Important, but not urgent

    and removed

    severity3: broken

    on Oct 1, 2020
12. atscott commented on Nov 17, 2020

    

    atscott

    on Nov 17, 2020

    Contributor

    More actions

    Closing as duplicate of #13523 for the

    <p><a [routerLink]="['two', {outlets:{secondary:['three']}}]">Navigate to /two(secondary:three)</a> = NOK(cannot match "two" segment)</p>
    

    This should instead be:

    a [routerLink]="[{outlets:{primary: 'two', secondary:['three']}}]">Navigate to /two(secondary:three)</a> = NOK(cannot match "two" segment)</p>
    

    While the empty path child redirect is somewhat similar to #10726 but slightly different. In this case, I'm not sure the empty path parent with an empty path child redirect in the secondary outlet is a good idea - this effectively creates a situation where you would not be able to close the outlet. If you have a burning desire to see this added, please submit a new issue that is specific to that request.
13. atscott

    closed this as completedon Nov 17, 2020
14. angular-automatic-lock-bot commented on Dec 19, 2020

    

    angular-automatic-lock-botbot

    on Dec 19, 2020

    More actions

    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.}
15. angular-automatic-lock-bot

    locked and limited conversation to collaborators on Dec 19, 2020