Fix display: contents
nodes not being cloned with the wrong owner
#1826
Reference in New Issue
Block a user
No description provided.
Delete Branch "@jpiasecki/contents-fix-updates"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR fixes two issues with
display: contents
implementation:display: contents
set is a leaf, it won't be cloned after the initial tree is built. The added test case covers this scenario.display: contents
nodes not to be cloned during layout. I don't have a minimal reproduction for this one, unfortunately. It was discovered in the Expensify app: https://github.com/Expensify/App/issues/65268, along with a consistent reproduction. In that specific case, it seems to be heavily tied toreact-native-onyx
, which is a state management library.The latest updates on your projects. Learn more about Vercel for Git ↗︎
@j-piasecki has imported this pull request. If you are a Meta employee, you can view this in D78084270.
This pull request was exported from Phabricator. Differential Revision: D78084270
@j-piasecki merged this pull request in facebook/yoga@c7c85621fc.
Pull request closed