angular.js, branch v1.0.4 chore(release): cut the 1.0.4 bewildering-hair release 2013-01-23T18:57:51+00:00 Igor Minar 2013-01-22T19:17:23+00:00 652feebd8678d27cb3c1f2bbd72de07a375f328a 






docs(changelog): release notes for 1.1.2 and 1.0.4
2013-01-23T18:57:51+00:00

Igor Minar

2013-01-23T06:53:51+00:00

16ccbc4f61dea60817699abac3b923618d8ce1c5












chore(changelog.js): improve the changelog script
2013-01-23T18:57:51+00:00

Igor Minar

2013-01-23T06:49:00+00:00

072d45fd012d6b6208d938fc376d1815b7f6120f












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







chore(Rakefile): skip build parallelization on Travis
2013-01-21T15:50:24+00:00

Igor Minar

2013-01-21T15:43:41+00:00

6df60aff527e1ae13815a14fe3994b471e623a5b

Due to a infrastructure change on Travis starting JVMs in forked
processes doesn't currently work. Since we don't really care that
much about the build speed on Travis, I'm going to disable it there.

Related issue: https://github.com/travis-ci/travis-ci/issues/845





Due to a infrastructure change on Travis starting JVMs in forked
processes doesn't currently work. Since we don't really care that
much about the build speed on Travis, I'm going to disable it there.

Related issue: https://github.com/travis-ci/travis-ci/issues/845







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

sergiopantoja

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

e7a080d6e602bf0346b7bbad9503ada6dedbbe1c












docs(contribute): adding npm install to step-by-step
2013-01-19T05:33:58+00:00

Will Moore

2013-01-18T20:57:59+00:00

661a7287641ef1056fe19bb2b8e3a851e08d13bd

npm install is listed in the dependencies section of the contribute guide but
is missing from the step-by-step. This adds it as step 4.





npm install is listed in the dependencies section of the contribute guide but
is missing from the step-by-step. This adds it as step 4.







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