Skip to content

fix: remove ability to use findComponent with DOM selector #896

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Aug 29, 2021
Merged

fix: remove ability to use findComponent with DOM selector #896

merged 1 commit into from
Aug 29, 2021

Conversation

xanf
Copy link
Collaborator

@xanf xanf commented Aug 28, 2021

This brings VTU2 behavior in line with VTU1
Closes #689

@xanf xanf force-pushed the xanf-remove-find-component-dom-selector branch from 6616e67 to f09cc09 Compare August 28, 2021 12:34
@xanf xanf mentioned this pull request Aug 28, 2021
Merged
@lmiller1990
Copy link
Member

Thanks!

@lmiller1990 lmiller1990 merged commit ad2adfe into vuejs:master Aug 29, 2021
@xanf xanf mentioned this pull request Oct 3, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

findAllComponents() returning the same component twice?
2 participants
@xanf @lmiller1990