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

fix($resolve): use resolvefn result,not parent resolved value of same name #1360

Merged
merged 1 commit into from
Sep 12, 2014

Conversation

christopherthielen
Copy link
Contributor

Made resolve values ignore any keys that we're actively trying to
resolve, when they also exist in some parent state. Made $$resolves
persist so they can be picked up by a child state in a later digest()
fixes #1317
fixes #1353

…me name

Made resolve values ignore any keys that we're actively trying to
resolve, when they also exist in some parent state.  Made $$resolves
persist so they can be picked up by a child state in a later digest()
fixes #1317
fixes #1353
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Strange behavior on resolve and $scope inheriting resolvers with the same name over childs
1 participant