-
Notifications
You must be signed in to change notification settings - Fork 273
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: get host component names on render (modified) #1306
Conversation
@pierrezimmermannbam @MattAgn In order to simplify code, reduce error handling I've added back lazy detection to |
Codecov ReportBase: 95.13% // Head: 96.07% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #1306 +/- ##
==========================================
+ Coverage 95.13% 96.07% +0.93%
==========================================
Files 46 49 +3
Lines 3205 3308 +103
Branches 483 497 +14
==========================================
+ Hits 3049 3178 +129
+ Misses 156 130 -26
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
well done 👍 |
This is based on #1304, but since that was external PR I've moved it as internal repo PR with added proposed changes:
detectHostElementNames
fromgetHostComponents()
configureHostElementNamesIfNeeded
to be called inrender
getHostElementNames
.Summary
Fixes #1302 by detecting host component names in
render
to prevent running auto detection in externalact
which fails for some users.Test plan
Added a test case where I call getHostComponentNames wrapped in act after a render and expect it does not throw