-
-
Notifications
You must be signed in to change notification settings - Fork 237
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
preserveTimezones
has no effect
#784
Comments
## [10.20.1](v10.20.0...v10.20.1) (2025-01-04) ### Bug Fixes * break/continue stops whole template, [#783](#783) ([5f1a4cf](5f1a4cf)) * enumerate plain objects in where/where_exp, [#785](#785) ([#788](#788)) ([25ef104](25ef104)) * preserveTimezones support for RFC2822 date, [#784](#784) ([59cf3c0](59cf3c0))
Please try |
It is working in
Also, the parsing doesn't seem to work if
However, it works if the space is removed, as with the input |
We can support time zones without minutes. But not for cases when it’s not a valid init string for JavaScript Date. As T is required for ISO9601. You can check whether it’s a LiquidJS issue or JavaScript issue by passing the string to ‘new Date’. |
On version
10.20.0
,preserveTimezones
doesn't seem to work at all.Actual output: (machine local timezone is UTC-7)
2025-01-01 21:04:05 -0700
Expected output:
2025-01-02 03:04:05 -0100
The text was updated successfully, but these errors were encountered: