-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
proposal: expose time.Location extend string for zone transitions #68367
Comments
why is it necessary to expose this data? and from the looks of it, just extends is insufficient to describe all the time zone transitions correctly? |
@seankhliao |
I don't think that's sufficient information to capture zone transitions, exposing it doesn't seem appropriate if it's incomplete. |
I agree that just the extend string is not enough to handle timezone transitions. It only predicts future transitions, it doesn't cover past ones. In any case this seems like something that belongs more in a third party library. |
I understand that the extend string may not capture all zone transitions comprehensively. However, the ability to predict future transitions still holds significant value. While it is true that the extend string focuses on future transitions and may not cover past ones, this limitation can be clearly documented. |
To provide zone info to the device, do we have to display the current zone location ? |
Varsayılan bölge olarak |
Proposal Details
When zoneinfo is needed, it is parsed from the files in the
/usr/share/zoneinfo/
directory.This implementation works only on Unix systems.
I recently discovered that this value is stored in the
extend
field of thetime.Location
struct.I use this value to send to other devices.
I propose adding a getter function to retrieve this value:
func (l *Location) Extend() string
The text was updated successfully, but these errors were encountered: