palantir/blueprint

Switch from inputRef to ref for Inputs

Open

#4,763 建立於 2021年6月14日

在 GitHub 查看
 (1 留言) (2 反應) (0 負責人)TypeScript (20,263 star) (2,167 fork)batch import
P2Package: coreStatus: to triageType: breaking changeType: enhancementhelp wanted

描述

Environment

  • Package version(s): v4 alpha
  • Browser and OS versions: all

Feature request

Blueprint v4 is switching elementRef to the "simpler, more straightforward" ref for non input elements. Can we also do the same for inputs that use inputRef. This would help with consistency of the library. Also for a less important reason, the massively popular React Hook Form is difficult to use if inputs do not have ref point to the actual input ref.

貢獻者指南

技術棧
typescriptreact
領域
frontend
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Understanding of React refsFamiliarity with Blueprint Input components
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
70
研究方向
Examine the Input components in the Blueprint library (e.g., InputGroup, TextArea) that currently use inputRef prop. Replace the inputRef references with ref, ensuring backward compatibility if needed. Check the existing documentation and tests for these components. No linked PR or specific maintainer comments are available; the main source is the wiki link in the issue.