Datepicker can no longer bind to a string date representation

[cen1]

Maybe I am missing something but this could be a regression.

Datepicker can no longer bind to a string representation of a Date. If I receive a JSON object from REST API that contains date as "1989-07-12T22:00:00.000+0000" it should be possible to bind it directly to datepicker. This used to work in 0.12.x but seems to be broken in 0.14.2.

Plunker: http://plnkr.co/edit/JLqDTMNl9tlQ5E831c4x?p=preview
example.js line 4

[icfantv]

@cen1, please do not use the issues forum for support related requests. Rather, please follow the instructions here. The issues forum is reserved for bugs.

This was intentionally changed due to cross browser issues and more. It is documented here. ng-model must be a date object. There were too many issues in parsing user strings so we now require a date object.

Additionally, this is also a duplicate of #4662, #4554, #4424, #4324, and probably more. Please search both open and closed issues before entering anything.

[wesleycho]

This is an intentional breaking change, as one can see in the changelog here.

There are cross-browser issues with supporting it as a string, so we removed support.

[icfantv]

@cen1, solutions were posted in those other issues. If you know that all your dates from the server are in a certain format you can use an HTTP interceptor to convert them to date objects - or you can do it in your own service. Whatever you want.

And yes. You need to pass in a JS Date object so you will need to construct one on your end.

[cen1]

Sorry for not seeing other issues.
It seems to me that this could be solved without breaking it. If there was an extra option to tell datepicker in what format to expect the string for example.

[wesleycho]

No, because of how munged the logic was, where state was difficult to follow, and the cross-browser issues with string representations is completely unsolvable - it was a broken feature without a fix.