Standard HTML attributes on components are interpreted as props and return a warning-like message

[robyedlin]

I'm not sure if this is a bug, but I get a Volar message on the class attribute of a component when class is not a defined prop.

<TableRow v-for="item in items" class="text-gray-500">

Hovering over class show the following message:

Property 'class' does not exist on type '{ ... }'. ts(2339)

I'm not 100% sure, but I think that standard HTML attributes on components are expected to pass through to the root element of the component. So I'm not sure if a warning is necessary.

[sethidden]

Works fine for me in the template from npm init vue@next then changed App.vue on line 11 to:

<HelloWorld msg="You did it!" v-for="i in [1,2,3]" class="text-gray-500" />

Can you provide a repo with a minimal repro?

Maybe this'll help, but it's shot in the dark. Throwing it in since it's related to the class/className stuff
#592

Related #552

[robyedlin]

@sethidden I repeated your procedure and I got this:

It only returns the warning if props are defined and class or any standard HTML attribute name is not included in the props definition

This isn't a big deal, but I'm not sure it's a TS 2339 error.

[sethidden]

Ah, I can reproduce it too. This happens if you run npm init vue@next and answer "No" to every question it asks you (so also "no" when it asks you if you want to setup TypeScript). Then if you add class="hello" on line 11 you'll have this in App.vue

[robyedlin]

@sethidden Actually I can see it when using ts as well.

[AlmarAubel]

@johnsoncodehk It looks like this issue still exists in version v.0.29.6

[johnsoncodehk]

@AlmarAubel this is a similar but different problem, see #592.