Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork3.3k
Don't override ref property when not configured to.#2252
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
Conversation
codesandbox-cibot commentedAug 21, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
This pull request is automatically built and testable inCodeSandbox. To see build info of the built libraries, clickhere or the icon next to each commit SHA. |
PSpSynedra commentedAug 21, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Unfortunately I cannot get the "Test Published Artifact expo (pull_request)" to pass. Can I run the failing test locally on my machine to fix the issue? |
✅ Deploy Preview forreact-redux-docs ready!
To edit notification comments on pull requests, go to yourNetlify project configuration. |
The current behavior of
connectis to always pass along a ref property, event when the optionforwardRefwas not truthy or preset.This pull request
undefinedref.The error in the following use case is also fixed with this pull-request:
NOTE:
My initial intend was to remove the use of
React.forwardRef(...)completely, but this would have broken the compatibility with React prior to version 19.