angular.js/src/ng/directive, branch v1.0.3 fix(ngClassOdd/ngClassEven): support shrinking/reordering in repeaters 2012-11-26T20:33:45+00:00 Igor Minar 2012-11-23T21:46:58+00:00 6f18adedef60ddb972a446046270f98c4ac18bb7 We need to watch $index in addition to cssClasses because only then we can correctly respond to shrinking or reordered repeaters. Closes #1076 
We need to watch $index in addition to cssClasses because only then
we can correctly respond to shrinking or reordered repeaters.

Closes #1076
fix(ngRepeat): support mostly-stable repeating for primitives 2012-11-26T20:33:45+00:00 Igor Minar 2012-11-23T21:43:30+00:00 cde2f1a868ffacdc592803358130587fd73aca7b I'm reverting changes that were originally done to ngRepeat to fix #933, because these are now not necessary after the previous changes to keep ngModel always synced with the DOM. 
I'm reverting changes that were originally done to ngRepeat to fix #933,
because these are now not necessary after the previous changes to keep
ngModel always synced with the DOM.
fix(ngModel): sync ngModel state with scope state 2012-11-26T20:33:45+00:00 Igor Minar 2012-11-23T21:40:01+00:00 6a831495dedc81e995bba276084eb3b23643557a In cases when we reuse elements in a repeater but associate them with a new scope (see #933 - repeating over array of primitives) it's possible for the internal ngModel state and the scope state to get out of sync. This change ensure that the two are always sync-ed up even in cases where we reassociate an element with a different (but similar) scope. In the case of repeating over array of primitives it's still possible to run into issue if we iterate over primitives and use form controls or similar widgets without ngModel - oh well, we'd likely need a special repeater for primitives to deal with this properly, even then there might be cornercases. Closes #933 
In cases when we reuse elements in a repeater but associate
them with a new scope (see #933 - repeating over array of
primitives) it's possible for the internal ngModel state and
the scope state to get out of sync. This change ensure that
the two are always sync-ed up even in cases where we
reassociate an element with a different (but similar) scope.

In the case of repeating over array of primitives it's still
possible to run into issue if we iterate over primitives and
use form controls or similar widgets without ngModel - oh well,
we'd likely need a special repeater for primitives to deal
with this properly, even then there might be cornercases.

Closes #933
fix(ngRepeat): attempt to simplify and improve existing fix for #933 2012-11-26T19:39:00+00:00 Igor Minar 2012-11-26T19:25:38+00:00 00e7e3141819e14ced3279fa5dfb8eba4ff89e5f I'm keeping this in for future reference. The issue with this solution is that if we shift() the first item in the array, the whole repeater DOM will be rebuilt from scratch, we need to do better than that. 
I'm keeping this in for future reference. The issue with this solution
is that if we shift() the first item in the array, the whole repeater
DOM will be rebuilt from scratch, we need to do better than that.
docs(api): add ngRequired to input/select/textarea directives 2012-11-25T00:19:47+00:00 Dean Sofer 2012-11-09T00:15:50+00:00 55150a669a8496b597267a522955f5cecda7b5d9 Closes #1202 
Closes #1202
docs(ngList): fix typo 2012-11-11T10:25:40+00:00 Josh Adams 2012-11-05T20:42:54+00:00 7550f90a57f7a875d22de31293885e73abd76593 






docs(ngHide): Fix typo and make it more in line with ngShow
2012-11-11T09:37:59+00:00

Christian Vuerings

2012-11-09T13:44:00+00:00

60acba38402f0c0804e72272fde78c9f3c94a0c4












fix(select): select option with a label of 0 is not shown
2012-10-31T22:03:48+00:00

Sudhir Jonathan

2012-10-21T07:27:27+00:00

d981c2a3ecfaf572a836c7533ee3a9553aae327d

Bug caused by the use of the `||` operator to replace all non-truthy
values with an empty string. Changed to replace only `undefined` values.

Closes #1401





Bug caused by the use of the `||` operator to replace all non-truthy
values with an empty string. Changed to replace only `undefined` values.

Closes #1401







fix(*): name all anonymous watch functions in Angular
2012-09-11T23:39:46+00:00

Shyam Seshadri

2012-07-06T09:53:40+00:00

2c6aa4c300073ef27fcce4c112646985d81a4fe4

This will allow us to see function names in Batarang and debugger.

Closes #1119





This will allow us to see function names in Batarang and debugger.

Closes #1119







fix(ng-repeat) to work with primitive types
2012-09-11T23:38:42+00:00

Zhenbo Zhang

2012-05-08T21:00:38+00:00

f7a8f17fc72f603de11ca89170bc8d1cad4dae6a