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.