Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Composition API: rendered instead of a child component

See original GitHub issue

EDIT: This seems to be Composition API related. The button does not get rendered because I use <component :is="componentType"> and componentType is coming from setup() which does not get called. In vue-test-utils I could pass localVue that would have Vue.use(Composition). Is there a way for this here?

I’m rendering a component that has several child components. My buttons could not be found. At first I thought it’s a shallow render by default but that’s not the case.

<ProfileImage> gets rendered without a problem <FileUpload> too

But instead of <Button>s I’m seeing  in the html output.

Is this because it’s a one word component that also shares name with an HTML element? Or that shouldn’t be an issue?

The tested component and also <ProfileImage> and <Button> use composition API.

Thanks!

Issue Analytics

State:
Created 3 years ago
Reactions:2
Comments:5 (1 by maintainers)

Top GitHub Comments

1reaction

afontcucommented, Apr 1, 2020

Hi Martin! We haven’t explored an integration with the Composition API or the beta of Vue 3, so I would say this is an expected issue 😃 We’ll work on that as soon as things get a bit more stable.

Thanks!

0reactions

MartinMalindacommented, Apr 1, 2020

OK! I didn’t notice any issues after Vue.use was done correctly in test setup.