[DevTools] Allow renaming Host Component props#35735
Merged
eps1lon merged 1 commit intofacebook:mainfrom Feb 9, 2026
Merged
Conversation
hoxyq
approved these changes
Feb 9, 2026
Contributor
hoxyq
left a comment
There was a problem hiding this comment.
Surprised that this wasn't reported
This file contains hidden or 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
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.
Summary
Renaming props only considered Fibers without an instance (e.g. Function Components) and Class Components. However, Host Components have an instance but don't implement
forceUpdatethus crashing the frontend. Now we only useforceUpdatefor Class Components like we do in all the other places where we useforceUpdate. Otherwise we useoverridePropsRenamePathregardless of theinstancewhich allows renaming props of Host Components.Found with Claude + Opus 4.6
How did you test this change?