Fallthrough attributes strictly checking for `v-bind="$attrs"`

[ferferga]

Vue - Official extension or vue-tsc version

2.2.10

VSCode version

1.100.0

Vue version

3.5.13

TypeScript version

5.8.3

System Info

package.json dependencies

Steps to reproduce

• Open the reproduction link
• Run npm run check

What is expected?

The $attrs TypeScript's symbol is found inside v-bind, regardless of it's location.

What is actually happening?

The $attrs is not detected properly, and attributes are not being inferred

Link to minimal reproduction

https://stackblitz.com/edit/vue3-vite-typescript-starter-tqjmhyir

Any additional comments?

No response

[KazariEX]

I think we cannot correctly analyze whether an expression depends on a certain value, as it's too complex.

[ferferga]

@KazariEX I guessed so 😔.

In a project of mine, I've worked with ts-morph, so I was interested in taking the plunge and attempt to PR this. However, getting the descendants of a node (and getting the AST symbol of $attrs, which would be necessary to achieve full compatibility, so reassignments like const attrs = $attrs inside inline function handlers and things like that work properly) was really costly performance-wise (at least in this project of mine), so much it would be impractical.

Is there any strong reason why we can't make useAttrs accept a type signature that overrides the automatic inference? Exactly like useTemplateRef, which gets automatically typed by the element is being ref'ed in template but can also be casted manually like this:

const element = useTemplateRef<HTMLImageElement>('image')

So with what I'm proposing it would be:

const attrs = useAttrs<MyCoolAndCustomType>()

And MyCoolAndCustomType will always take precedence over the automatic inference of $attrs.
What do you think?

[KazariEX]

Yes, now it doesn't do this just because it has no type parameters. You can make a pr to add generals for useAttrs at core repo.