| Age | Commit message (Collapse) | Author |
|
|
|
select (one/multiple) could not chose from a list of objects, since DOM requires string ids.
Solved by adding index formatter, which exposed incorrect handling of formatters in select
widgets.
|
|
anything while evaluting JSON.
|
|
- native parser delegation
- $xhr change to use native parser
|
|
We came across a major performance regression due to this change.
I'm reverting it until we find a better solution.
This reverts commit 23fc73081feb640164615930b36ef185c23a3526.
|
|
|
|
|
|
- RegExp parser is rearly used, feature, and one should not have RegExps
in views anyways, so we are removing it
BACKWARD INCOMPATIBLE CHANGE!!!
|
|
Closes #169
|
|
ng-errors
|
|
|
|
Support ISO 8601 extended format datetime strings (YYYY-MM-DDTHH:mm:ss.SSSZ) as defined
in EcmaScript 5 throughout angular. This means that the following apis switched from
YYYY-MM-DDTHH:mm:ssZ to YYYY-MM-DDTHH:mm:ss.SSSZ (note the added millis) when representing dates:
- angular.Date.toString
- angular.String.toDate
- JSON serialization and deserialization (used by json filter, $xhr and $resource)
|
|
|
|
|