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 loaded module with no child states creates bad err message #3

Closed
christopherthielen opened this issue Nov 2, 2016 · 1 comment
Closed

Lazy loaded module with no child states creates bad err message #3

christopherthielen opened this issue Nov 2, 2016 · 1 comment
Labels
bug
Milestone
1.0.0-beta.4

Comments

@christopherthielen
Copy link
Member

christopherthielen commented Nov 2, 2016 •
edited

If a module is lazy loaded but does not have any forChild states defined, the parent module states are re-registered. This creates an error message saying the state is already defined

screen shot 2016-11-02 at 5 55 14 pm
@christopherthielen christopherthielen added this to the 1.0.0-beta.4 milestone Jan 21, 2017
@christopherthielen
Copy link
Member Author

this is fixed in beta.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
1.0.0-beta.4
Development

No branches or pull requests
1 participant
@christopherthielen