Repository navigation
fix: find elements and components inside multi-root functional components - #2971
Merged
cexbrayat merged 1 commit intoOct 15, 2026
Merged
Conversation
…ents findComponent on a functional component returning an array wrapped the fragment anchor, so html/text lost nested roots and find/findComponent found nothing. Collect the roots of the functional instance like VueWrapper does, reading its current subTree.
❌ Deploy Preview for vue-test-utils-docs failed. Why did it fail? →
|
commit: |
cexbrayat
approved these changes
Oct 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Follow-up to #2568 / #2579.
findComponent(Func)on a functional component returning an array gives aDOMWrapperaround the fragment anchor, so:html()/text()lose nested arrays and slotsfind/findAll/getfind nothingfindComponent/findAllComponentsfind nothingThe wrapper now collects its roots with
getRootNodes()(likeVueWrapper) and resolves the functional instance from the fragment anchor, reading its current subTree so results stay in sync after a re-render.Note: like a multi-root
VueWrapper,html()no longer prints<!---->for empty (null/false) roots.isVisible()/classes()/attributes()/trigger()still target the anchor.Repro on 2.5.1: playground