fix: react-cons-elem should not hoist router comp #14828
Merged
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.
Thanks @budarin for the reproduction repo. It helps a lot. This PR is a follow-up to #14536. In this PR we set the initial value of the map
HOISTED
to be thejsxScope
, which is the ancestry hoisting scope (if hoisted) orpath.scope
. Then we updateHOISTED
when it it actually hoisted. In this way, theComponent
in the test case won't be hoisted because its parentRoute
's hoisting scope is the BlockStatement, instead of the ArrowFunction to which we never hoisted due to no advantages.