angular.js/test/ng, branch v1.1.0 revert: fix(ng-repeat) to work with primitive types 2012-08-31T20:59:03+00:00 Igor Minar 2012-08-31T20:41:10+00:00 5e9041818bca770c9261a3963e05dbb3c7ca2f06 this was accidentaly merged in. the commit is not ready yet and we don't have CLA signature. This reverts commit 98d489712eff7559bce87ae53bd242112a875c1a. 
this was accidentaly merged in. the commit is not ready yet
and we don't have CLA signature.

This reverts commit 98d489712eff7559bce87ae53bd242112a875c1a.
test(locationSpec): fix broken tests after vojta's commit 2012-08-30T23:25:23+00:00 Igor Minar 2012-08-30T23:25:02+00:00 a62c7b8b4eaba2979e19c3b0438d67fcdc5f9e1a 






fix(ng-repeat) to work with primitive types
2012-08-30T22:20:40+00:00

Zhenbo Zhang

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

0a71753ce3f4fe241e15fa489617b82710be4648












feat($interpolate): provide contextual error messages
2012-08-30T21:50:22+00:00

Brian Ford

2012-07-19T21:07:00+00:00

d804bbcd51ec83bee1f4a3ccd42c3bd7eb38a988

if an exception occurs during interpolation of a string
(e.g. name() in "Hello, {{name()}}!" throws an exception) we now print
an error message with the expression that was being evaluated when the
exception was thrown.





if an exception occurs during interpolation of a string
(e.g. name() in "Hello, {{name()}}!" throws an exception) we now print
an error message with the expression that was being evaluated when the
exception was thrown.







fix(docs) typo
2012-08-27T21:59:19+00:00

Misko Hevery

2012-06-02T23:25:52+00:00

c269eb3d261dffd95e2827df9f7c5f55d6fdc8c7












fix($compile): denormalize directive templates
2012-08-13T21:33:56+00:00

Igor Minar

2012-08-11T07:13:10+00:00

dfe99836cd98c2a1b0f9bde6216bd44088de275a

Since developers are allowed to customize start/end interpolation
strings, but third-party directive creators don't know about these
customizations, we should standardize on {{ }} in templates of
reusable (third-party) directives. During the compilation, these
templates are then denormalized to use whatever the custom
start/end symbol is, effectively translating the template into the
syntax of the runtime environment.

This addresses an issue raised at http://goo.gl/e8VPV

Existing code should not be affected by this change since project
that do use custom interpolation markers are not expected to use
{{ }} in existing directive templates.





Since developers are allowed to customize start/end interpolation
strings, but third-party directive creators don't know about these
customizations, we should standardize on {{ }} in templates of
reusable (third-party) directives. During the compilation, these
templates are then denormalized to use whatever the custom
start/end symbol is, effectively translating the template into the
syntax of the runtime environment.

This addresses an issue raised at http://goo.gl/e8VPV

Existing code should not be affected by this change since project
that do use custom interpolation markers are not expected to use
{{ }} in existing directive templates.







refactor($compile): code cleanup
2012-08-13T16:48:23+00:00

Igor Minar

2012-08-11T06:46:42+00:00

0f37194fb7ce67c3719626d9e21d95a66538a0e4












fix(ngPluralize): fixes ng-pluralize when using non-standard start/end symbols
2012-08-13T16:48:23+00:00

Brian Ford

2012-07-19T08:10:12+00:00

e85774f709b9f681b0ff8d829b07568b0f844a62

Closes #1134





Closes #1134







style(ngPluralizeSpec): fix indentation
2012-08-13T16:48:22+00:00

Igor Minar

2012-08-11T00:37:06+00:00

44345c74decfd2e303ada9c958af8e9a07bb8336












feat($interpolate): expose start/end symbols in run phase
2012-08-13T16:48:22+00:00

Igor Minar

2012-08-11T05:24:42+00:00

58f121a5c293ed57043e22ed526fdf99642fca81

previously the startSymbol() and endSymbol() getters were exposed only via provider
in the config phase





previously the startSymbol() and endSymbol() getters were exposed only via provider
in the config phase