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
I'd like to be able to use calendar-dates queries with date formats that aren't exactly mm/dd/YYYY or YYYY-mm-dd, specifically I'd like ISO8601 format YYYY-mm-ddTHH:MM:SS[+|-]HH:MM not to be rejected.
Optionally, YYYY-mm-ddTHH:MM:SSZ or YYYYmmddTHHMMSSZ
For this specific use case (Fullcalendar), changing our format validation from a strictly equals to a starts with would work fine, i.e. if we evaluated only what's before the T.
Possible complications: do we want to apply the expanded format to other date validations?
These are under /dates/. I definitely need those under /calendar-dates/
(These are the smaller tasks that should happen in order to complete this work)
[ ]
Completion criteria
Current date formats are still valid (with the new one, as decided)
Querying with start and dates in the ISO formats returns results as expected (without errors) /v1/calendar-dates/?per_page=500&min_start_date=2024-12-01T00%3A00%3A00-05%3A00&max_start_date=2025-01-01T00%3A00%3A00-05%3A00
returns the same results as /v1/calendar-dates/?per_page=500&min_start_date=2024-12-01&max_start_date=2025-01-01
References/resources/technical considerations
(Is there sample code or a screenshot you can include to highlight a particular issue? Here is where you reinforce why this work is important)
The text was updated successfully, but these errors were encountered:
What we’re after
I'd like to be able to use calendar-dates queries with date formats that aren't exactly
mm/dd/YYYY
orYYYY-mm-dd
, specifically I'd like ISO8601 formatYYYY-mm-ddTHH:MM:SS[+|-]HH:MM
not to be rejected.Optionally,
YYYY-mm-ddTHH:MM:SSZ
orYYYYmmddTHHMMSSZ
For this specific use case (Fullcalendar), changing our format validation from a strictly equals to a starts with would work fine, i.e. if we evaluated only what's before the
T
.Possible complications: do we want to apply the expanded format to other date validations?
These are under /dates/. I definitely need those under
/calendar-dates/
Related ticket(s)
None
Action item(s)
(These are the smaller tasks that should happen in order to complete this work)
Completion criteria
Current date formats are still valid (with the new one, as decided)
Querying with start and dates in the ISO formats returns results as expected (without errors)
/v1/calendar-dates/?per_page=500&min_start_date=2024-12-01T00%3A00%3A00-05%3A00&max_start_date=2025-01-01T00%3A00%3A00-05%3A00
returns the same results as
/v1/calendar-dates/?per_page=500&min_start_date=2024-12-01&max_start_date=2025-01-01
References/resources/technical considerations
(Is there sample code or a screenshot you can include to highlight a particular issue? Here is where you reinforce why this work is important)
The text was updated successfully, but these errors were encountered: