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
We have had a publisher publish "valid" data with an awardDate as 2022-02-29, this causes python's datetime.date.fromisoformat(date) to error with day is out of range for month (which is correct error).
This could be handled at the application (in this case the datastore) that consumes this data to ignore this and replace it with a default or it could be (I think more usefully) raised as validation error.
The text was updated successfully, but these errors were encountered:
ThreeSixtyGiving/standard#283 would allow us to resolve this in schema, I think - although it's described as "format", I believe the "date" format disallows impossible dates, such as 29th Feb in non-leap-years
We have had a publisher publish "valid" data with an awardDate as 2022-02-29, this causes python's
datetime.date.fromisoformat(date)
to error withday is out of range for month
(which is correct error).This could be handled at the application (in this case the datastore) that consumes this data to ignore this and replace it with a default or it could be (I think more usefully) raised as validation error.
The text was updated successfully, but these errors were encountered: