You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 29, 2019. It is now read-only.
When loading an entity with angular's $http/$resource, angular creates the model by using native JSON function and all dates/datetimes are converted to String or Number.
The Datepicker wait for a ng-Model value must be a Date object - currently it get a error!
Workaround:
Convert the String (or Number) to Date in the Datapicker directive.
There are in angularjs a jsonStringToDate function in date $filter that makes this job
The text was updated successfully, but these errors were encountered:
@dipold We've started down the "automatically covert strings to Dates" route in the https://github.com/angular-ui/ui-date and it was a disaster. There are simply way too many formats that would could automatically handle. The proper solution is to use formatters / parsers (or a custom directive that would take care of conversions).
Going to close this one as we are just discussing plugging into the ngModel machinery in #612. Let's move the discussion there.
The problem:
When loading an entity with angular's $http/$resource, angular creates the model by using native JSON function and all dates/datetimes are converted to String or Number.
The Datepicker wait for a ng-Model value must be a Date object - currently it get a error!
Workaround:
Convert the String (or Number) to Date in the Datapicker directive.
There are in angularjs a jsonStringToDate function in date $filter that makes this job
The text was updated successfully, but these errors were encountered: