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

feat(ionicContent): use child scope instead of isolate scope #668

Closed
wants to merge 1 commit into from

Conversation

ajoslin
Copy link
Contributor

@ajoslin ajoslin commented Feb 24, 2014

Adds new '$ionicBindParent' service, which takes an object containing
binding definitions (similar to angular directive isolate scope
definition). Allows binding of any scope and attributes from any parent
scope, letting us do normal parent -> child scope binding without having
to create isolate scopes.

Closes #555.

We could refactor many current isolate scope directives to use this, as well, and fix many inheritance / controller problems.

Adds new '$ionicBindParent' service, which takes an object containing
binding definitions (similar to angular directive isolate scope
definition).  Allows binding of any parent scope & directive attributes
to a child scope, letting us do normal parent -> child scope binding
without having to create isolate scopes.

Closes #555
@ajoslin ajoslin closed this Feb 24, 2014
@ajoslin
Copy link
Contributor Author

ajoslin commented Feb 24, 2014

Realized a flaw in the way I was doing ionicBind

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.

Angular form not in $scope, when put inside <content>
1 participant