> but how the heck is Jan 1st 2022 put in the 2023 year?
This only happened shortly after midnight on January 1st. So I guess this is somehow related to different time zones/offsets.
This only happened shortly after midnight on January 1st. So I guess this is somehow related to different time zones/offsets.
2022-12-31 23:16:54.013
And then our UI converted this entry into one with 2023
(it correctly assumes that the string is in UTC and then converted it to local time +1h)
A linter should probably flag any format that mixes "week year" with month and days. It's really for use by itself or with payroll week number.