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

Support the [property] / bind-property syntax in AngularJS #12198

Closed
mhevery opened this Issue Jun 23, 2015 · 4 comments

Comments

Projects
None yet
4 participants
@mhevery
Member

mhevery commented Jun 23, 2015

Goal

In order to support the ng2migration effort the AngularJS needs to learn how to process the Angular 2 property binding syntax

Syntax Variants

  • [property]
  • bind-property

Semantics

AngularJS should set up a watch on the expression and write the value of the expression to the Attributes class which sits on Node Element. This will allow the ng2migration.js to $observe changes not the Attributes and pass them onto the component controller.

NOTE: by writing the value to the Attribute this in essence means that AngularJS will not differentiate between the attributes / properties which Angular 2 does. Given that AngularJS semantics are to write to attributes and that it does not support WebComponents this is a reasonable approximation.

@lgalfaso

This comment has been minimized.

Show comment
Hide comment
@lgalfaso

lgalfaso Jun 24, 2015

Member

Does Angular2 have a security model defined for expressions?

Member

lgalfaso commented Jun 24, 2015

Does Angular2 have a security model defined for expressions?

@mhevery

This comment has been minimized.

Show comment
Hide comment
@mhevery

mhevery Jun 24, 2015

Member

@lgalfaso not yet, but we should. Would you like to work on that?

Member

mhevery commented Jun 24, 2015

@lgalfaso not yet, but we should. Would you like to work on that?

@lgalfaso

This comment has been minimized.

Show comment
Hide comment
@lgalfaso

lgalfaso Jun 25, 2015

Member

@mhevery I am interested in working on that

Member

lgalfaso commented Jun 25, 2015

@mhevery I am interested in working on that

@IgorMinar

This comment has been minimized.

Show comment
Hide comment
@IgorMinar

IgorMinar Jul 1, 2015

Member

per discussion in https://docs.google.com/document/d/1xvBZoFuNq9hsgRhPPZOJC-Z48AHEbIBPlOCBTSD8m0Y/edit# I'm going to close this issue for now so that we don't give wrong impression as to what is actually going to happen. The main problem with adding this syntax into Angular 1 core is that it fragments the api/docs/etc and exposes large api surface that we'd need to maintain - which is especially challenging because of the semantical differences between Angular 1 and 2.

We can reopen this issue in the future if needed.

Member

IgorMinar commented Jul 1, 2015

per discussion in https://docs.google.com/document/d/1xvBZoFuNq9hsgRhPPZOJC-Z48AHEbIBPlOCBTSD8m0Y/edit# I'm going to close this issue for now so that we don't give wrong impression as to what is actually going to happen. The main problem with adding this syntax into Angular 1 core is that it fragments the api/docs/etc and exposes large api surface that we'd need to maintain - which is especially challenging because of the semantical differences between Angular 1 and 2.

We can reopen this issue in the future if needed.

@IgorMinar IgorMinar closed this Jul 1, 2015

@mattdsteele mattdsteele referenced this issue Aug 27, 2017

Merged

Add AngularJS #6

5 of 5 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment