palantir/blueprint

Switch from inputRef to ref for Inputs

Open

#4,763 opened on Jun 14, 2021

View on GitHub
 (1 comment) (2 reactions) (0 assignees)TypeScript (20,263 stars) (2,167 forks)batch import
P2Package: coreStatus: to triageType: breaking changeType: enhancementhelp wanted

Description

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.

Contributor guide

Tech stack
typescriptreact
Domain
frontend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Understanding of React refsFamiliarity with Blueprint Input components
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
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.