Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

docs(guide/Expressions): one-time binding of object literals #11982

Closed
wants to merge 1 commit into from

Conversation

pholly
Copy link
Contributor

@pholly pholly commented May 29, 2015

One time binding of object literals are treated differently than simple expressions. Added a link under the Value stabilization algorithm section to Ben Nadel's article describing how object literals's keys are checked for undefined.

…bject literals under Value stabilization algorithm

One time binding of object literals are treated differently than simple expressions. Added a link to Ben Nadel's article describing how object literals's keys are checked for undefined.
@googlebot
Copy link

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project, in which case you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.


  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If you signed the CLA as a corporation, please let us know the company's name.

@pholly
Copy link
Contributor Author

pholly commented May 29, 2015

Signed CLA

@googlebot
Copy link

CLAs look good, thanks!

petebacondarwin pushed a commit that referenced this pull request Jun 1, 2015
…bject literals under Value stabilization algorithm

One time binding of object literals are treated differently than simple expressions. Added a link to Ben Nadel's article describing how object literals's keys are checked for undefined.

Closes #11982
netman92 pushed a commit to netman92/angular.js that referenced this pull request Aug 8, 2015
…bject literals under Value stabilization algorithm

One time binding of object literals are treated differently than simple expressions. Added a link to Ben Nadel's article describing how object literals's keys are checked for undefined.

Closes angular#11982
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants