[CLOSED] Default date format for Type="Date" RecordField

[r_honey]

I updated to latest version of Ext.Net on one of the projects after a long time today (around 7-8 months).
Immediately I noticed RecordField with Type="Date" no longer parse dates sent from server (in universal serializable format).

I believe the default DateFormat for Ext.Net Date RecordField used to be the same, has the same changed in recent past?

[Vladimir]

Please clarify, did you update from SVN or use last official release?

[r_honey]

I updated from SVN (the latest commit for 1.x branch), and I can confirm, if I set the DateFormat to this:
Y-m-dTh:i:s
things return back to normal.

[Vladimir]

In 1.3 default date format is "yyyy-MM-ddThh:mm:ss.u" (ms is added)

[r_honey]

Hmmm.. I better create a RecordField derived class and reset again for myself to old one.
Thanks for the quick replied vlad...

[Daniil]

The related note about Ext.NET v2.

There is the RenderMilliseconds property of ModelField (ModelField is the substitution of RecordField).

By default, it's false and, respectively, milliseconds are not rendered.

Setting RenderMilliseconds to true causes milliseconds to be rendered.

[r_honey]

Great, thanks for the update. It would have been useful to back-port it to v1.

[Daniil]

Thanks for the suggestion. We will consider it.

[geoffrey.mcgill]

Personally I feel this change (adding milliseconds) in v1.3 was a mistake, and should be treated as a defect. Maybe we should fix v1.4? That of course would lead to another breaking change.

We could add .RenderMilliseconds [bool] in v1.4 to provide API consistency between v1.4 and v2.x.

In the vast majority of cases Millisecond precision is not required. The DateTime Class was not really even designed for sub-second precision.

Any thoughts on reverting back to just "yyyy-MM-ddTHH:mm:ss" format, thereby removing the Milliseconds from being serialized by default?

[geoffrey.mcgill]

I should also note, in v2, the current default functionality is to NOT include Milliseconds. So if upgrading from v1.3 to v2.x you might run into a breaking change anyways.

Certainly my preference is to remove Millisecond rendering from the default functionality of v1.4... and, add .RenderMilliseconds [boolean] property to v1.4. The functionality of v2.x would then not change and upgrading from the latest 1.x build to 2.x wouldn't involve a Breaking Change, at least as far as this property/functionality is concerned.