Currently, date columns that are not explicitly configured with a source format and timezone cause the advanced filter dialog to break when applying a range filter.
I've modified the behaviour as follows:
Defaults are now applied if the dateFormat object is not set in the column configuration.
I've updated the default date format (which wasn't being used) from YYYY/MM/DDD HH:mm:ss to ISO8601 (YYYY-MM-DD"T"HH:mm:ss.SSS). It's parsed in forgiving mode, which means it should work correctly for truncated ISO8601 date time strings (eg. 2018-01-01, 2018-01-01T03:00 etc will all work).
I've also added some more tests to verify that the defaults apply correctly and that I haven't broken anything when source and output date formats are configured.
Currently, date columns that are not explicitly configured with a source format and timezone cause the advanced filter dialog to break when applying a range filter.
I've modified the behaviour as follows:
dateFormatobject is not set in the column configuration.YYYY/MM/DDD HH:mm:ssto ISO8601 (YYYY-MM-DD"T"HH:mm:ss.SSS). It's parsed in forgiving mode, which means it should work correctly for truncated ISO8601 date time strings (eg.2018-01-01,2018-01-01T03:00etc will all work).I've also added some more tests to verify that the defaults apply correctly and that I haven't broken anything when source and output date formats are configured.
This resolves #790.
Before:
After: