-
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
SlotFill: unify registry and fill implementation #68056
base: trunk
Are you sure you want to change the base?
Conversation
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Size Change: -110 B (-0.01%) Total Size: 1.84 MB
ℹ️ View Unchanged
|
Unification of both
SlotFill
registries (context providers) into one that handles both types. The two types ofSlot
are distinguished by atype: 'children'
ortype: 'portal'
field.Also the
Fill
component is now only one. It looks at the type of the currently registered slot and conditionally renders a portal.Only the
Slot
components remain separate for now, because their implementation and even the prop types are wildly different.This is still a draft, to verify how unit and e2e tests are going.