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

Possible router bug/unexpected behavior #10702

Closed
tuurbo opened this issue Aug 11, 2016 · 1 comment · Fixed by #10707
Closed

Possible router bug/unexpected behavior #10702

tuurbo opened this issue Aug 11, 2016 · 1 comment · Fixed by #10707

Comments

@tuurbo
Copy link
Contributor

tuurbo commented Aug 11, 2016

I'm submitting a ... (check one with "x")

[x] bug report
[ ] feature request
[ ] support request
https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior
HeroComponent is being recreated with each child navigation

Expected/desired behavior
HeroComponent shouldn't be recreated with each child navigation.

I was having the issue in my private app, so checked a plunker from angular.io and noticed the same issue there as well.

Reproduction of the problem
plunker was taken from the angular.io docs and just added console.logs and displayed the time
http://plnkr.co/edit/ey56dehV7rwfxkneK0oW?p=preview

Here is where i got the original plunker from angular.io https://angular.io/docs/ts/latest/guide/ngmodule.html#!#lazy-load

Please tell us about your environment:

  • Angular version: 2.0.0-rc.5
  • Browser: [Chrome 52]
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants