palantir/blueprint

DateInput2 weird timezone UX when typing incomplete date

Open

#5,443 建立於 2022年7月19日

在 GitHub 查看
 (1 留言) (0 反應) (0 負責人)TypeScript (20,263 star) (2,167 fork)batch import
P1Package: datetimeType: bughelp wanted

描述

Environment

  • Package version(s): @blueprintjs/datetime2 as of #5440

Steps to reproduce

  1. visit docs preview from #5440, or build the repo at https://github.com/palantir/blueprint/commit/fbe3c9e3662f0d0dc4096e082c4f3f014e0ab01f
  2. type "7/19/202" into DateInput2

Actual behavior

Incomplete date results in a very unexpected timezone shown in the TimezoneSelect

Expected behavior

Don't parse strange/invalid timezones like this

Possible solution

??

貢獻者指南

技術棧
typescriptreact
領域
frontend
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
React experienceDate/time handling basics
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
70
研究方向
Examine the DateInput2 component's date parsing logic, particularly how incomplete dates are handled and how the timezone is displayed. Refer to the linked PR #5440 and commit fbe3c9e3662f0d0dc4096e082c4f3f014e0ab01f. Look in the @blueprintjs/datetime2 package for the parsing function and the TimezoneSelect component to understand how the timezone string is generated.
DateInput2 weird timezone UX when typing incomplete date · palantir/blueprint#5443 | Good First Issue