Skip to content

Proposal: Ref Forwarding on all Components #901

Closed
@emplums

Description

@emplums

Description

It's become clear through our collaboration with other teams that setting up ref forwarding on each component would make Primer React Components a lot more convenient to work with. Previously, we've added ref forwarding to components on an as-needed basis, but as Primer React Components begins to be used in more complex applications, it's harder to predict which components will need ref forwarding.

Plan of Action

I'm proposing that we refactor one component at a time and have a PR for each component so we don't miss anything in the review process as some components may take a bit of refactoring.

I would prefer to do all of the components in one big release, but since most of the DS Engineers are working on deadline intensive projects at the moment and I'd like close eyes on each PR, I am planning on doing a batch of high priority components in one major release, and then the rest of the components in another release later when we have more resources for reviewing all the PRs/helping refactor components.

First Batch of Components

  • all SelectMenu Components
  • Buttons
  • Box (since some other components are based on Box, I think we'll need to set ref forwarding on Box so ref gets passed down properly)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions