Add support for Fibers in ReactDOMComponentTree and ReactTreeTraversal #8232
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.
This adds precaching to ReactDOMFiber. I.e. adding a handle from the DOM node to the internal Fiber. This means that we need to expose an internal handle to the reconciler.
We use duck typing inside ReactDOMComponentTree and ReactTreeTraversal to figure out if it is a Fiber or Stack instance.
The new failing tests are failing because this is now able to actually fire events onto Fibers and then the result of those events are incorrect where as they were ignored before.
In ReactTreeTraversal we traverse parent based on the type of internal instance it is passed. We could probably optimize this by doing the detection outside each loop and duplicate the loops.
If the parent is a Fiber it may have to traverse multiple steps until it finds a HostComponent since we don't have pointers directly to the next host container.
This will allow us to use the event system with Fiber.