-
Notifications
You must be signed in to change notification settings - Fork 668
Components only returning a render function from setup aren't considered components #1596
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
Labels
Comments
You could try just adding another condition to I have no idea what will happen - this easiest way to find out would just be going to |
LeBenLeBen
added a commit
to LeBenLeBen/vue-test-utils
that referenced
this issue
Jul 1, 2020
12 tasks
LeBenLeBen
added a commit
to LeBenLeBen/vue-test-utils
that referenced
this issue
Jul 12, 2020
LeBenLeBen
added a commit
to LeBenLeBen/vue-test-utils
that referenced
this issue
Jul 12, 2020
LeBenLeBen
added a commit
to LeBenLeBen/vue-test-utils
that referenced
this issue
Aug 29, 2020
LeBenLeBen
added a commit
to LeBenLeBen/vue-test-utils
that referenced
this issue
Aug 30, 2020
lmiller1990
pushed a commit
that referenced
this issue
Aug 30, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Subject of the issue
Components using the Composition API that return a render function from
setup
are not considered valid Vue Components by the internal validator. Consequently, they can’t be used as stubs.Steps to reproduce
Have a component using the composition API without template and where the
render
function is returned by thesetup
function:When trying to mount it like this:
Vue-test-utils throws the following error:
Theses components’ code can be found here.
Expected behaviour
Vue components using solely a render function through setup should be considered valid components.
Possible Solution
Adapt isVueComponent method to handle this specific kind of components. But I’m not sure how this should be done, hints welcome so I can potentially submit a PR.
The text was updated successfully, but these errors were encountered: