angular.js/src, branch v1.0.4 fix(ngResource): correct leading slash removal. 2013-01-22T19:32:27+00:00 pavelgj 2013-01-08T22:19:40+00:00 4439e393198d6a1657c02c098e1b13212c3f1db6 Fixed an issues with ngResource param substitution where it was incorrectly removing leading slash when param was followed by a non-slash character. Ex: '/:foo/:bar.baz/:aux' params = { foo: 'aaa', bar: undefined, aux: undefined } The above params were incorrectly producing '/aaa.baz' but now it results in '/aaa/.baz'. 
Fixed an issues with ngResource param substitution where it was incorrectly removing leading slash when param was followed by a non-slash character.
Ex:
'/:foo/:bar.baz/:aux'

params = {
  foo: 'aaa',
  bar: undefined,
  aux: undefined
}

The above params were incorrectly producing '/aaa.baz' but now it results in '/aaa/.baz'.
docs(q): added testing information 2013-01-22T19:32:27+00:00 Miško Hevery 2012-12-14T13:49:22+00:00 b49c3a1a1efc85b31053481eea450c7be407957c 






fix(angular.equals): relax the comparison for undefined properties
2013-01-22T15:35:06+00:00

Igor Minar

2013-01-22T06:00:15+00:00

c7addd488677307c6d2b35c7656179fbe6d80999

in 5ae63fd3 the comparison was made consistent but strict, so that

angular.equals({}, {foo: undefined}) // always returns false

this turns out to cause issues for data that is being roundtripped via network
and serialized via JSON because JSON.stringify serializes {foo: undefined} as {}.

Since angular.equals() behaved like this before the 5ae63fd3 in 50% of the cases,
changing the behavior in this way should not introduce any significant issues.

Closes #1648





in 5ae63fd3 the comparison was made consistent but strict, so that

angular.equals({}, {foo: undefined}) // always returns false

this turns out to cause issues for data that is being roundtripped via network
and serialized via JSON because JSON.stringify serializes {foo: undefined} as {}.

Since angular.equals() behaved like this before the 5ae63fd3 in 50% of the cases,
changing the behavior in this way should not introduce any significant issues.

Closes #1648







docs(jqLite): fix typo
2013-01-20T17:59:43+00:00

sergiopantoja

2013-01-20T16:52:17+00:00

e7a080d6e602bf0346b7bbad9503ada6dedbbe1c












fix(ngSwitch): don't leak when destroyed while not attached
2013-01-18T08:03:42+00:00

danilsomsikov

2013-01-11T17:21:13+00:00

89303fd2dccb780bea594b16b8ec85d9f3bd8f92

The leak can occur when ngSwich is used inside ngRepeat or any other
directive which is destroyed while its transcluded content (which
includes ngSwitch) is not attached to the DOM.

Refactor ngSwitch to use controller instead of storing data on compile
node. This means that we don't need to clean up the jq data cache.
Controller reference is released when the linking fn is released.

Closes #1621





The leak can occur when ngSwich is used inside ngRepeat or any other
directive which is destroyed while its transcluded content (which
includes ngSwitch) is not attached to the DOM.

Refactor ngSwitch to use controller instead of storing data on compile
node. This means that we don't need to clean up the jq data cache.
Controller reference is released when the linking fn is released.

Closes #1621







docs(exceptionHandler): document testing
2013-01-18T07:11:02+00:00

Fred Sauer

2013-01-17T02:01:03+00:00

1f8be1ca66b312fdc396403f01ee8aae9371577a

Update src/ng/exceptionHandler.js

Here's an iniitla attempt at documenting how one might write a
test using $exceptionHandlerProvider. The key take-away is the use
of this pattern:

it(...

 module(...
   $exceptionHandlerProvider.mode('log');
 });

 inject(...
 );

});





Update src/ng/exceptionHandler.js

Here's an iniitla attempt at documenting how one might write a
test using $exceptionHandlerProvider. The key take-away is the use
of this pattern:

it(...

 module(...
   $exceptionHandlerProvider.mode('log');
 });

 inject(...
 );

});







docs(rootScope): correct code examples
2013-01-18T07:11:02+00:00

Matthew Browne

2013-01-15T16:49:42+00:00

cbc2024092b326cc7e46d4defc4bf2248bbeb835












docs(ngMock.$httpBackend): fix variable declaration
2013-01-18T05:15:20+00:00

Fred Sauer

2012-12-27T22:40:45+00:00

f179a63dd49050bec65cfd7f755413d2ed90a03b












fix(angular.equals): consistently compare undefined object props
2013-01-18T01:49:07+00:00

Igor Minar

2013-01-18T00:53:30+00:00

a6b2ee785b91ce69fe265d423c18ea7a899c922d

previously:

a = {};
b = {x:undefined};
angular.equals(a, b) == angular.equals(b, a) // returns false.

both should return false because these objects are not equal.

unlike in implemented in #1695 the comparison should be stricter
and return false not true. if we need to relax this in the future
we can always do so.

Closes #1648





previously:

a = {};
b = {x:undefined};
angular.equals(a, b) == angular.equals(b, a) // returns false.

both should return false because these objects are not equal.

unlike in implemented in #1695 the comparison should be stricter
and return false not true. if we need to relax this in the future
we can always do so.

Closes #1648







feat($compile): support modifying the DOM structure in postlink fn
2013-01-17T20:57:36+00:00

Martin Probst

2013-01-08T19:11:51+00:00

66f051386e153f10bd2751a7cafb61404799adee

Support modifying the DOM structure in the post link function of a directive
by creating a defensive copy of the node list, as opposed to a live DOM list.
This is useful for directives to actually replace their entire DOM fragment,
e.g. with the HTML fragment generated by a 3rd party component (Closure, Bootstrap ...).
Fix the indentation of the compileNodes function (was one too little).





Support modifying the DOM structure in the post link function of a directive
by creating a defensive copy of the node list, as opposed to a live DOM list.
This is useful for directives to actually replace their entire DOM fragment,
e.g. with the HTML fragment generated by a 3rd party component (Closure, Bootstrap ...).
Fix the indentation of the compileNodes function (was one too little).