[compiler] Allow ref access in useImperativeHandle #30913
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Summary: Code within the useImperativeHandle callback is not executed during render, much like useEffect. We can apply the same rules around ref access to this callback. [ghstack-poisoned]
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This was referenced Sep 8, 2024
Merged
mvitousek
added a commit
that referenced
this pull request
Sep 8, 2024
Summary: Code within the useImperativeHandle callback is not executed during render, much like useEffect. We can apply the same rules around ref access to this callback. ghstack-source-id: 8e528397032a9fa1d023562f9be3672e136bf029 Pull Request resolved: #30913
|
Superseded by #30917 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Stack from ghstack (oldest at bottom):
Summary:
Code within the useImperativeHandle callback is not executed during render, much like useEffect. We can apply the same rules around ref access to this callback.