angular.js/test, branch v1.0.4

fix(ngResource): correct leading slash removal.

2013-01-22T19:32:27+00:00

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'.

fix(angular.equals): relax the comparison for undefined properties

2013-01-22T15:35:06+00:00

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

fix(ngSwitch): don't leak when destroyed while not attached

2013-01-18T08:03:42+00:00

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

fix(angular.equals): consistently compare undefined object props

2013-01-18T01:49:07+00:00

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

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).

fix($compile): do not wrap empty root text nodes in spans

2013-01-17T08:28:56+00:00

Closes #1059

fix(ngRepeat): correctly apply $last if repeating over object

2013-01-17T08:25:07+00:00

If the $last property is calculated from the original collectionLength
on an object and properties starting with $ were filtered out, then $last
is never applied and $middle is applied erroniously.

Closes #1789

fix(scenario): don't trigger input events on IE9

2013-01-17T07:30:16+00:00

input.enter() should trigger 'change' rather than 'input' event on IE9 because
input events on IE9 are broken and angular doesn't rely on them

fix($route): support route params not separated with slashes.

2013-01-16T17:42:35+00:00

Commit 773ac4a broke support for route parameters that are not seperated
from other route parts by slashes, which this change fixes. It also adds
some documentation about path parameters to the when() method and
escapes all regular expression special characters in the URL, not just
some.

fix($compile): safely create transclude comment nodes

2013-01-15T05:59:23+00:00

Closes #1740