…stonejs#3160

Properties in DatetimeType were not being carried through to
DatetimeField. Now resolved.

format property replaced by dateFormat and timeFormat properties.

Requires properly set parseFormat property (inclusing time zone format
(Z) to function correctly. We should be able to calculate this based on
the dateFormat and timeFormat properties and pass through form the Type
to the Field.

…g instead of hardcoding in DatetimeField.

Updated validation for options to reflect change from format to dateFormat, timeFormat and tzFormat.

dateFormat, timeFormat and tzFormat specified.

This removes the requirement for a parseFormat option to be specified.

The parseFormat option is still available, and if supplied is appended
along with the calculated format to the default list.

…3160

Placeholder for time field now displays correct format.

the same array being shared by all Datetime field instances.

Fixed test 'should throw when format is not a string'. Now fails if
exception is not thrown, rather than timing out.

timeFormat and tzFormat.

Altered test for validation of the default format when a parseFormat
is specified.

Previously, if a parseFormat is specified, this became the only
acceptable format, even if a different display format is defined.
If the display format differs from the parse format, the field will
not validate as populated from the database.

Now, if a parseFormat (or formats, in an array) is specified it will
be added to the list of acceptable formats (the default array plus
the display format).