-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
editoast: use DateTime with timezone in work schedule API #9656
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I sincerely like that change ❤️
f01986e
to
fd55d57
Compare
fd55d57
to
cf5690b
Compare
If this is deemed too intrusive for a bugfix, we could fix only the GET side of the API as a first step, and take more time to merge the POST side (and adapt the various users). |
7063a02
to
506a107
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Check with @Morgane-SJK no problem we are already using TZ everywhere in elt code
The timezone was stored in the database, but was stripped at the HTTP API boundary. This is a breaking change: the timezone is required when submitting a work schedule, and is always returned when projecting a work schedule. Signed-off-by: Simon Ser <contact@emersion.fr>
506a107
to
f65d82c
Compare
The timezone was stored in the database, but was stripped at the HTTP API boundary.
This is a breaking change: the timezone is required when submitting a work schedule, and is always returned when projecting a work schedule.
Closes: #9652