feat(ngBindOnce) && feat{ngRepeatOnce} Bind to the DOM once with no watchers #5408

rhettl · 2013-12-14T20:22:45Z

This feature should include:

ngBindOnce
ngBindTemplateOnce
ngRepeatOnce

This feature would allow a developer to:

bind to the DOM one time
Reduce the number of watchers on e the page, Esp in situations of nested repeaters

It is for data that:

doesn't need to be dynamic
is loaded once and forgotten
cannot be loaded from the server side code

Narretz · 2013-12-15T13:06:04Z

+1

Narretz · 2013-12-15T13:06:51Z

or, alternatively, a way to suspend and re-enable watches.

kennethlynne · 2013-12-15T13:52:29Z

+1

manland · 2013-12-15T16:32:53Z

+1

erwinmombay · 2013-12-15T19:07:27Z

+1

rhettl · 2013-12-16T18:13:23Z

I have been trying to figure out how to add labels after creating an issue.
Since I cannot figure out how, could a moderator possibly add labels to this?

Thank you greatly!

lord2800 · 2013-12-17T05:13:37Z

+1

scottmas · 2013-12-20T07:43:21Z

+1

cburgdorf · 2013-12-20T08:11:26Z

+1

sebholstein · 2013-12-20T10:26:45Z

+1

CMRahman · 2013-12-20T17:22:36Z

+1

nicolacity · 2013-12-20T19:47:30Z

+1

adzialocha · 2013-12-20T21:10:50Z

+1

panrafal · 2013-12-21T21:30:47Z

+1

red-0ne · 2013-12-21T23:34:55Z

+1

red-0ne · 2013-12-21T23:35:35Z

the enable/disable variant could be great

melnikov77 · 2013-12-22T20:40:51Z

+1

CWSpear · 2013-12-22T20:46:56Z

+1

macl · 2013-12-23T05:04:28Z

+1

dpiatek · 2013-12-23T11:39:41Z

+1

sukei · 2013-12-23T11:52:21Z

+1

dehru · 2013-12-23T16:27:10Z

+1

runxc1 · 2013-12-23T23:29:19Z

+1

rhettl · 2013-12-24T00:04:03Z

While Disable/Enable might be nice, I don't think it is necessary. It would be easy enough to wrap the DOM element in an ngSwitch or ngIf to deal with the on/off. Same with nested repeats -- if the first ngRepeat is a normal one and the nested ngRepeats are bindOnce, one can have static content that still changes when the program tells it.

In short, I think that it may be nice to have the enable/disable feature, but if it is easier to just have an ngBindOnce without the enable/disable feature, then don't worry about it and possibly add it in the future if it is needed.

uglow · 2013-12-24T00:23:16Z

+1

warnerandy · 2013-12-24T04:44:13Z

+1

guybedo · 2013-12-24T15:40:05Z

+1

mofas · 2013-12-24T16:23:33Z

+1

ghost · 2013-12-27T15:50:19Z

+1

ohana54 · 2014-01-14T21:20:42Z

+1

Pierrebleroux · 2014-01-22T07:16:39Z

+1

pawelszymanski · 2014-01-22T22:23:17Z

+1

IlanFrumer · 2014-01-28T00:18:14Z

+1

RobertSasak · 2014-01-30T14:26:23Z

+1

mb-dev · 2014-02-04T20:40:15Z

+1

matjaz · 2014-02-05T16:21:49Z

a way to suspend and re-enable watches would be a great addition to this. for example stock ticker with push data.
templates can have complex layout so using ngSwitch would mean a lot of duplication.

MichielDeMey · 2014-02-07T18:37:59Z

+1

I'd like to see this in Angular as well. I'm currently using Pasvaz's Bindonce and it works perfectly.

ghost · 2014-02-09T10:23:17Z

We currently use bindonce and this: http://blog.scalyr.com/2013/10/31/angularjs-1200ms-to-35ms/
Its available at https://github.com/scalyr/angular

…ngular#5408 Signed-off-by: Josh Kurz <[email protected]>

…ngular#5408 Signed-off-by: Josh Kurz <[email protected]> fix(ngBindOnceDirsSpec.js): testing everything Signed-off-by: Josh Kurz <[email protected]>

mwilc0x · 2014-02-19T02:46:01Z

+1

ProLoser · 2014-02-19T20:29:07Z

Please check out #6354 for a better alternative proposal to bind-once

…ngular#5408 Signed-off-by: Josh Kurz <[email protected]> fix(ngBindOnceDirsSpec.js): testing everything Signed-off-by: Josh Kurz <[email protected]>

gautelo · 2014-04-12T21:12:33Z

Indeed, please do check out #6354, as @ProLoser suggests. It would give us some simple syntax to solve this, and more than this, instead of a series of additional directives.

HeberLZ · 2014-04-27T16:38:55Z

+1
Please implement this inside angular core! It would become a must use in many applications

Dbuggerx · 2014-04-27T23:06:31Z

+1

dsc8x · 2014-04-28T16:23:46Z

+1

MaxShv · 2014-05-21T04:40:55Z

+1

Expressions that start with `::` will be binded once. The rule that binding follows is that the binding will take the first not-undefined value at the end of a $digest cycle. Watchers from $watch, $watchCollection and $watchGroup will automatically stop watching when the expression(s) are bind-once and fulfill. Watchers from text and attributes interpolations will automatically stop watching when the expressions are fulfill. All directives that use $parse for expressions will automatically work with bind-once expressions. E.g. <div ng-bind="::foo"></div> <li ng-repeat="item in ::items">{{::item.name}};</li> Paired with: Caitlin and Igor Design doc: https://docs.google.com/document/d/1fTqaaQYD2QE1rz-OywvRKFSpZirbWUPsnfaZaMq8fWI/edit# Closes angular#7486 Closes angular#5408

ghost assigned IgorMinar Dec 20, 2013

donaldpipowitch mentioned this issue Feb 5, 2014

Keep interpolation information in DOM so that bootstrapping from prerendered html is possible #5406

Closed

joshkurz pushed a commit to joshkurz/angular.js that referenced this issue Feb 17, 2014

feat(ngBindOnceDirs.js): implementation of simple bindOnce directives a…

5671a2d

…ngular#5408 Signed-off-by: Josh Kurz <[email protected]>

joshkurz mentioned this issue Feb 17, 2014

feat(ngBindOnceDirs.js): implementation of simple bindOnce directives #6284

Closed

btford added needs: public api labels Mar 5, 2014

georgebohnisch mentioned this issue Mar 23, 2014

feat(ngBindOnceDirs.js): implementation of simple bindOnce directives #6815

Closed

IgorMinar added the complexity: large label May 20, 2014

IgorMinar added high priority and removed complexity: large labels May 21, 2014

lgalfaso closed this as completed in cee429f May 23, 2014

Droogans mentioned this issue Jun 25, 2014

Protractor doesn't work with different binding directives ( eg. bindonce ) angular/protractor#842

Closed

feat(ngBindOnce) && feat{ngRepeatOnce} Bind to the DOM once with no watchers #5408

feat(ngBindOnce) && feat{ngRepeatOnce} Bind to the DOM once with no watchers #5408

Comments

rhettl commented Dec 14, 2013

Narretz commented Dec 15, 2013

Narretz commented Dec 15, 2013

kennethlynne commented Dec 15, 2013

manland commented Dec 15, 2013

erwinmombay commented Dec 15, 2013

rhettl commented Dec 16, 2013

lord2800 commented Dec 17, 2013

scottmas commented Dec 20, 2013

cburgdorf commented Dec 20, 2013

sebholstein commented Dec 20, 2013

CMRahman commented Dec 20, 2013

nicolacity commented Dec 20, 2013

adzialocha commented Dec 20, 2013

panrafal commented Dec 21, 2013

red-0ne commented Dec 21, 2013

red-0ne commented Dec 21, 2013

melnikov77 commented Dec 22, 2013

CWSpear commented Dec 22, 2013

macl commented Dec 23, 2013

dpiatek commented Dec 23, 2013

sukei commented Dec 23, 2013

dehru commented Dec 23, 2013

runxc1 commented Dec 23, 2013

rhettl commented Dec 24, 2013

uglow commented Dec 24, 2013

warnerandy commented Dec 24, 2013

guybedo commented Dec 24, 2013

mofas commented Dec 24, 2013

ghost commented Dec 27, 2013

ohana54 commented Jan 14, 2014

Pierrebleroux commented Jan 22, 2014

pawelszymanski commented Jan 22, 2014

IlanFrumer commented Jan 28, 2014

RobertSasak commented Jan 30, 2014

mb-dev commented Feb 4, 2014

matjaz commented Feb 5, 2014

MichielDeMey commented Feb 7, 2014

ghost commented Feb 9, 2014

mwilc0x commented Feb 19, 2014

ProLoser commented Feb 19, 2014

gautelo commented Apr 12, 2014

HeberLZ commented Apr 27, 2014

Dbuggerx commented Apr 27, 2014

dsc8x commented Apr 28, 2014

MaxShv commented May 21, 2014