Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
v0.5.0
-
None
Description
service.timezone value is correctly parsed in eagle backend service, but its not correctly parsed on ui side and its limited to UTC and GMT values only because of the way of calculating timezone is via UTC offset logic.
so values like "America/Los_Angeles" works fine on the backend codebased but throws un-parsable error on UI because it expects only UTC and GMT values.
this values are important to consider daylight saving time.