We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
From @Spyro92 on March 17, 2017 1:9
This is a:
My version of UI-Router is: 1.0.0-rc.1
When lazy loading states, any states registered in modules that are dependencies to the module being lazy loaded will not be registered.
in the example: lazy.foo is being registered, but not lazy.bar
it seems to be a timing issue, if you remove the dependency on lazy.bar from the module 'lazy' the state will be registered.
lazy.bar and lazy.foo should be registered
http://plnkr.co/edit/IfxBMmsZgKVAyxSZ7w0g?p=info
Copied from original issue: angular-ui/ui-router#3375
The text was updated successfully, but these errors were encountered:
Thank you for the excellent bug report with plunker
Sorry, something went wrong.
This is the same bug as ui-router/angular#40 and needs to be fixed in ui-router/core
4bdce47
Thanks for your quick work on this! Will ui-router/core v5.0.0 be going live with angular-ui/ui-router 1.0.0-rc.2?
No branches or pull requests
From @Spyro92 on March 17, 2017 1:9
This is a:
My version of UI-Router is: 1.0.0-rc.1
Bug Report
Current Behavior:
When lazy loading states, any states registered in modules that are dependencies to the module being lazy loaded will not be registered.
in the example: lazy.foo is being registered, but not lazy.bar
it seems to be a timing issue, if you remove the dependency on lazy.bar from the module 'lazy' the state will be registered.
Expected Behavior:
lazy.bar and lazy.foo should be registered
Link to Plunker that reproduces the issue:
http://plnkr.co/edit/IfxBMmsZgKVAyxSZ7w0g?p=info
Copied from original issue: angular-ui/ui-router#3375
The text was updated successfully, but these errors were encountered: