feat: handle fallthrough attributes in built-in components consistently #11140
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 is a naive approach for vuejs/rfcs#664
Why it's naive?
Given
Suspense
andTeleport
are not "real" components but abstractions for Vue's renderer, this is probably not the best approach because:cloneVNode
as, we're doing a workaround around the "workaround" that these 2 special components are.Extraneous non-props attributes were passed to component...
will still be displayed during development, givencomponentRenderUtils
is unaware that we're "hacking" this already manually.See also the comment I added to the codebase.
I'm leaving this open as a draft to gather feedback and some insights in how this could be done better, so later on I can keep going with Teleport, TransitionGroup and tests.
Checklist