Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix directive for route active #368

Merged
merged 1 commit into from
Mar 1, 2016
Merged

Fix directive for route active #368

merged 1 commit into from
Mar 1, 2016

Conversation

ggaulard
Copy link
Contributor

@ggaulard ggaulard commented Mar 1, 2016

This fix the directive that put a 'active' class on active link.
In a case with a 2 level of routeConfig the second level is not correctly define.

Fixed version
http://plnkr.co/edit/vleQ7C7Z0VBwrwx46UO3?p=preview

Original version
http://plnkr.co/edit/3ZbRYYzIxiiliP2Gbzm7?p=preview

@ggaulard ggaulard changed the title Fix update of link Fix directive for route active Mar 1, 2016
@ggaulard
Copy link
Contributor Author

ggaulard commented Mar 1, 2016

I forgot to specify the test scenario :s my bad.

Crisis Center -> Dragon Burning Cities
With Fix Version the "Dragon Burning Cities" Link is yellow 'active' class defined.
With the original version the "Dragon Burning Cities" is not updated.

I think the the ChildRoute doesn't fire event to the subscribe when the RootRouter change.
This may come from a bug in Angular2.

@PatrickJS
Copy link
Owner

LGTM

PatrickJS added a commit that referenced this pull request Mar 1, 2016
Fix directive for route active
@PatrickJS PatrickJS merged commit 889d175 into PatrickJS:master Mar 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants