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 (2,167 forks)batch import
P2Package: coreStatus: to triageType: breaking changeType: enhancementhelp wanted

Repository metrics

Stars
 (20,263 stars)
PR merge metrics
 (Avg merge 43d 10h) (27 merged PRs in 30d)

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

Research direction
Investigate the current usage of inputRef in Input components and plan to replace it with standard ref, ensuring backward compatibility or migration path.
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.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
React
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65