You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the validation and the actual date format being inconsistent, I just want to be sure whether this change is intentional and the format can be expected for the foreseeable future?
The text was updated successfully, but these errors were encountered:
The required date format for isPublicHoliday and isWorkDay seems to have changed from V2 to V3.
V2 makes use of dd-mm-yyyy
https://kayaposoft.com/enrico/json/v2.0/?action=isPublicHoliday&date=29-05-2022&country=zaf
However it seems that yyyy-mm-dd is now required for V3
https://kayaposoft.com/enrico/json/v3.0/isPublicHoliday/?date=2022-05-29&country=zaf
Passing a bogus string to V3 the validation still says that dd-mm-yyyy is required
https://kayaposoft.com/enrico/json/v3.0/isPublicHoliday/?date=20220529&country=zaf
{"error":"Invalid date '20220529'! Date string must be in format dd-mm-YYYY, e.g. 15-01-2035"}
With the validation and the actual date format being inconsistent, I just want to be sure whether this change is intentional and the format can be expected for the foreseeable future?
The text was updated successfully, but these errors were encountered: