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 }}
Repository navigation
aio(routing) live example is not working as expected #24638
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[ ] Feature request
[X ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
[ ] Other... Please describe:
Current behavior
Live example for the route and navigations is not working as expected live example
as per the documentation: 'You'd like to send the id of the current hero with the navigation request so that the HeroListComponent can highlight that hero in its list.'
sending the id as an optional parameter to the herosList component that will be used to highlight the selected hero is not working as expected (the selected hero is not getting highlighted).
It may be due to redirectTo, it breaks the optional parameter sent to the heroes component and we are not getting hero id in the herolist component.
Expected behavior
the selected hero should get highlighted (we should get the selected heroId as a part of params in the heroList component).
Minimal reproduction of the problem with instructions
Goto any of the heroes from the list. lets say - 12 Narco
Click Back from the hero details.
Narco should be highlighted (the optional parameter which we are passing from the hero detail component should be available in the params in the hero list component). which is not.
Activity
brandonroberts commentedon Jun 26, 2018
This issue is covered in my router guide updates PR. You can view the live example preview https://pr20023-a1643e3.ngbuilds.io/
brandonroberts commentedon Sep 26, 2018
Fixed via #20023
angular-automatic-lock-bot commentedon Sep 14, 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.