Skip to content

Conversation

@illiteratewriter
Copy link
Member

@illiteratewriter illiteratewriter commented Mar 8, 2023

#2089

  • Bug fix
  • New feature
  • Chore
  • Breaking change
  • There is an open issue which this change addresses
  • I have read the CONTRIBUTING document.
  • My commits follow the Git Commit Guidelines
  • My code follows the code style of this project.
  • My change requires a change to the documentation.
    • I have updated the documentation accordingly.
  • My change requires a change to Typescript typings.
    • I have updated the typings accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@illiteratewriter illiteratewriter requested review from aaronmars and removed request for aaronmars September 28, 2023 10:30
@aaronmars
Copy link
Collaborator

It seems like the pattern throughout the library is to use the innerRef pattern instead. I'm not defending that pattern (I think this forwardRef / ref pattern is the best and recommended way to go). I'm just wondering if this is the right place to introduce a new way of handling refs? Perhaps a larger effort to switch patterns with a breaking change?

@illiteratewriter
Copy link
Member Author

This can be merged along with #2695 I guess.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants