-
Notifications
You must be signed in to change notification settings - Fork 3k
inheriting resolvers with the same name over childs #1317
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
Comments
Hmmm... Likely related to #1212 Thanks for the detailed bug report. |
i want to know, what i need to do its normal for this plugin? for now i switch to 0.2.10 |
@christopherthielen This case is already addressed by your rewrite, yeah? |
I think the rewrite should address it, but I'll have to take a look at the plunkr to see exactly how the resolves are being inherited. Probably leave this open for now. |
Same Problem here ... I think this issue is not fixed now. |
Fix coming in #1360 |
I'm extending my resolvers objects using $.extend for adding some common code, one of them is adding a general resolver which is inherited and also defined by each child states, this works in version 0.2.10 but there is something weird in 0.2.11, because my child are inheriting the resolver one state up and is not using the own (this is happening in the controller of the state), i have this http://plnkr.co/edit/ewmHII?p=info plunker for see the issue, i'm using 0.2.10 for see the spected behavior, then i change to the last version (commenting and uncommenting) the problem can be seen in the console, in this example i'm emulating the use of a common resolver and printing the resolver in the state controller.
The text was updated successfully, but these errors were encountered: