palantir/blueprint

Support retrieving timezone metadata via properties other than IANA code

Open

#5,794 创建于 2022年12月9日

在 GitHub 查看
 (0 评论) (0 反应) (0 负责人)TypeScript (20,263 star) (2,167 fork)batch import
P2Package: datetimeType: feature requesthelp wanted

描述

Environment

  • Package version(s): datetime2 v0.9.6

Feature request

@blueprintjs/datetime2 supports getTimezoneMetadata() where you pass in a timezone IANA code. But sometimes I'd like to query for the metadata with other information, like the UTC offset.

When querying by only the offset, we know that one offset may correspond to multiple timezones. In these cases we may only care about the minimal set of timezones (see https://github.com/palantir/blueprint/issues/5793).

We could probably support this in the existing API:

function getTimezoneMetadata(offsetOrIanaCode: string, date?: Date): TimezoneMetadata | undefined;

贡献者指南

技术栈
typescriptreact
领域
frontend
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
familiarity with TypeScriptunderstanding of IANA timezone database
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
30
研究方向
Investigate the existing `getTimezoneMetadata` function in `@blueprintjs/datetime2`. Review the linked issue #5793 for context on handling multiple timezones per offset. The implementation should extend the function's parameter to accept either an IANA code or a UTC offset string, returning metadata for all matching timezones. Consider using the `Intl.DateTimeFormat` or `luxon` library for timezone resolution.