Open hasan-y-tr opened 2 months ago
There is no explicit changelog published but as the error message suggests date-time fields should have proper format; meaning that it must have timezone specified.
So, createDate should be like '2024-04-15T00:00:00Z'. You need to check if expecting a timezoned date-time value breaks any contract.
Based on https://datatracker.ietf.org/doc/html/rfc3339#section-5.6 i see partial-time
and time could be without timezone, so v3 is doing it too much restrictive. Only way is to revert into v2
Based on https://datatracker.ietf.org/doc/html/rfc3339#section-5.6 i see
partial-time
and time could be without timezone, so v3 is doing it too much restrictive. Only way is to revert into v2
partial-time
is part of the date-time
but time-offset
is also so the latter is required.
So the behaviour of requiring time-offset
is in line with the RFC and the issue therefor invalid. I suggest you use ajv.addFormat
to define your custom formats.
I have a schema as:
It does not validate the below date:
It fails on validation with the error below:
My settings are as below:
package.json
:I just had to downgrade to
"ajv-formats": "2.1.1"