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.

Sign up for GitHub

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

Jump to bottom

Lazy loading states in wrong order can cause states to be lost. #40

Closed
christopherthielen opened this issue Feb 4, 2017 · 1 comment
Closed

Lazy loading states in wrong order can cause states to be lost. #40

christopherthielen opened this issue Feb 4, 2017 · 1 comment
Labels
1.0
Milestone
1.0.0-beta.5

Comments

@christopherthielen
Copy link
Member

If you have a future state foo.** and you lazy load a NgModule with states in this order:

  • foo.bar
  • foo
  • foo.baz

The foo.bar state is "lost".

This is because instead of being queued until foo is ready, it attaches as a child to the future state foo.** which is then removed when foo is registered.
@christopherthielen christopherthielen added this to the 1.0.0-beta.5 milestone Feb 4, 2017
This was referenced Mar 17, 2017
Closed
Closed
@christopherthielen
Copy link
Member Author

Closing as duplicate of ui-router/core#46

christopherthielen added a commit to ui-router/core that referenced this issue Mar 27, 2017
@christopherthielen
test(lazyLoad): Failing test for ui-router/angular#40
773ff3a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
1.0
Projects
None yet
Milestone
1.0.0-beta.5
Development

No branches or pull requests
1 participant
@christopherthielen