This repository was archived by the owner on Apr 12, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 27.4k
one-time binding ng-options #10687
Milestone
Comments
can you please create a plunker that shows this issue? Thanks! |
Ok, I am able to reproduce this and know what is wrong |
lgalfaso
added a commit
to lgalfaso/angular.js
that referenced
this issue
Jan 8, 2015
Preserve the $watchDelegate on the watcher used to detect changes on the labels Closes angular#10687
lgalfaso
added a commit
to lgalfaso/angular.js
that referenced
this issue
Jan 9, 2015
Preserve the $watchDelegate on the watcher used to detect changes on the labels Closes angular#10687
petebacondarwin
added a commit
to petebacondarwin/angular.js
that referenced
this issue
Jan 12, 2015
Utilize the $watchDelegate on the watcher used to detect changes to the labels. Closes angular#10687 Closes angular#10694
petebacondarwin
added a commit
to petebacondarwin/angular.js
that referenced
this issue
Jan 12, 2015
Utilize the $watchDelegate on the watcher used to detect changes to the labels. Closes angular#10687 Closes angular#10694
Why cannot we use |
I am not sure if this will provide a performance benefit as the expression |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
According to docs, when using a directive that takes an expression, we are able set one-time binding as so:
`
However, this doesn't seem to work with ng-options, tried (1.3.0 - 1.38)
ng-options="o as o for o in ::things"
If I place ::things in a binding it works.
ng-options="o as o for o in {{::things}}"
The text was updated successfully, but these errors were encountered: