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
Is your feature request related to a problem or unsupported use case? Please describe.
The API lacks support for date ranges spanning DST to STD transitions due to new query parameter validation.
The start and end dates of a range must have the same UTC offset.
Example:
'Europe/Paris' is UTC+02:00 in STD and UTC+01:00 in DST.
When querying a range from 15th of October to the 30th of October, the API will respond a 422 unprocessable entity.
Describe the solution you'd like
I want to pass a date range that shares a timezone, not just a UTC offset.
I've added an extra step in the frontend to ensure that both the start and end dates have the same UTC offset.
Describe alternatives you've considered
Add a timezone parameter when querying the API?
Discovery, Documentation, Adoption, Migration Strategy
If you want to understand DST and STD abbreviation, please take a look here
The text was updated successfully, but these errors were encountered:
Feature Request
Is your feature request related to a problem or unsupported use case? Please describe.
The API lacks support for date ranges spanning DST to STD transitions due to new query parameter validation.
The start and end dates of a range must have the same UTC offset.
Example:
'Europe/Paris' is UTC+02:00 in STD and UTC+01:00 in DST.
When querying a range from 15th of October to the 30th of October, the API will respond a 422 unprocessable entity.
Describe the solution you'd like
I want to pass a date range that shares a timezone, not just a UTC offset.
I've added an extra step in the frontend to ensure that both the start and end dates have the same UTC offset.
Describe alternatives you've considered
Discovery, Documentation, Adoption, Migration Strategy
If you want to understand DST and STD abbreviation, please take a look here
The text was updated successfully, but these errors were encountered: