Vetur: Intellisense not always working in computed properties

[Soresu]

• [ x] I have searched through existing issues
• [ x] I have read through docs
• [ x] I have read FAQ

Info

• Platform: Win 10
• Vetur version: 0.23.0
• VS Code version: 1.42.1

Problem

Intellisense is not working when the computed property returns a reference from this, and the component has props, even its empty. I belive this is the same as #1509 , but the return part is not visible in the picture.

Reproducible Case

You can check the example repo, I've changed Counter.vue file

[nekosaur]

This might be platform specific? This is on OS X

But on W10 I got the same result as you

[alexandrmiee]

I reproduce this bug on
Win10, Ubuntu
Vetur 0.24.0
Soleved by set @returns option to all computed props

[F0rsaken]

It's connected with this https://vuejs.org/v2/guide/typescript.html#Annotating-Return-Types
and issue with circular dependencies in TypeScript >= 3.4.x

Even if you don't use TS, Vetur does and not annotating return type of computed kind of breaks this context.

[cerino-ligutom]

Getting this as well. What's odd is when the return keyword is there, it breaks:

When not:

[F0rsaken]

@cerino-ligutom when the return is used, TypeScript wants to infer the return type of the computed test that depends on this, but this depends on also computed test, but test....

And we go into recursive loop....

[cerino-ligutom]

@cerino-ligutom when the return is used, TypeScript wants to infer the return type of the computed test that depends on this, but this depends on also computed test, but test....

And we go into recursive loop....

Then how come that's not the case in methods? Or is it just the current typedefs for Vue2?

[F0rsaken]

I actually don't know. I never thought about it, but it's probably because methods and computed have different way of typing

[F0rsaken]

ok, I found it. ComponentOptions are based on generics. And every generic is taken almost literraly, except for Computed's, that are wrapped in another generic Accessor AND mapped with index signatures and operator keyof like this:

and that mapping is where TypeScript fails unfortunately.

[Soresu]

@F0rsaken And how is it connecting to props? When I don't use props in the component, the intellisense is fine.

[F0rsaken]

@Soresu props are also deeply nested in generics and mapped with index signatures.

I'm only guessing, but you aren't not using type: ... field. This is where you declare a prop's type, therefore the type don't need to be infered.

But actually, props don't use this.... so maybe it's something different....

[yoyo930021]

If vetur.useWorkspaceDependencies: true,
you will use [email protected] in vetur and not have any error.
The error is happened when using typescript@^3.x.x.
It's a type definition error in Vue lib.
Ref: vuejs/vue#11235

[dav245]

I have been fighting with similar issue last few days. My problem was slightly different. When i defined props inside of SFC, intellisense just stopped working. Using [email protected] actually solved it. Thank you.

[yoyo930021]

Duplicate of #1509

[octref]

Writing this once for all. The bug is that when you have computed, TypeScript cannot infer this type correctly and cannot provide correct auto-completion and type-checking. Simplest repro case:

TS upstream issue, and it seems TS wouldn't fix it: https://github.com/microsoft/TypeScript/issues/30854#issuecomment-485893681

Your solutions:

• Downgrade TS and enable vetur.useWorkspaceDependencies. However, you don't get all the new features including optional chaining.
• Set vetur.validation.interpolation: false. You'll not get any template error checking.
• Write JSDocs to annotate computed property return types.
• Convert your project to use TS + Vue, and manually write computed property return types.

But I'm not using TS! Why should I care?

Vetur uses TypeScript to figure out the type of your Vue component and provide all kinds of language features (completion, diagnostic error), even for Vue+JS components. Of course you can turn off the diagnostic error, but in return you will not get many of the features brought to you by TypeScript.

[rchl]

Writing this once for all.

It's not very discoverable at the end of some random issue. As I said elsewhere, it would be good to make this prominent. Either by having a pinned issue or including in documentation.

[Uninen]

I created a PR for adding this in the FAQ: https://github.com/vuejs/vetur/pull/2250

[OmgImAlexis]

This seems related but I'm using ts so I'm not sure what todo at this point. If it's unrelated please let me know and I'll open a seperate issue.

Convert your project to use TS + Vue, and manually write computed property return types.

The last suggestion doesn't seem to help, or maybe I'm doing it wrong? I tried both ways I know of returning a type and neither seems to fix the Vetur issue yet it does show the type in intellisense.

I have v0.31.3 of Vetur, Vue v3.0.5 and Typescript v4.1.3 installed.