-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix for local lookup of closure components #14421
Conversation
This looks good to me! @Serabe - Would you mind reviewing also? |
72c3826
to
5e067bd
Compare
Missed a semicolon, should pass CI now |
Also, just to make it clear to others, this PR is targeting |
Should we add a test for rerendering with a different component with different scope? In any case, LGTM. |
Good idea! @sglanzer - Would you have time to add that test? |
Yeah, I can add that test - so e.g. swap from local to global scope on the rerender? |
@sglanzer - Yes, exactly. |
5e067bd
to
ede16ca
Compare
Thank you again @sglanzer! |
The source/module in the env when creating a closure component is correct, but wasn't accessible/used when rendering the closure component in a child context. This fix retains the source/module and sets the env appropriately when a closure component is rendered.