Completions broken in setup function return object literal for vue

[yoyo930021]

Bug Report

🔎 Search Terms

completions return 'object literal shorthands'

🕗 Version & Regression Information

• This changed between versions 4.2.0 and 4.2.3

⏯ Playground Link

Playground link with relevant code

💻 Code

import { defineComponent } from '@vue/runtime-core'

export default defineComponent({
  name: 'App',
  setup () {
    const waitingForAutocomplete = true;

    const a = {
      wait // get `waitingForAutocomplete`
    }

    return {
      wait // don't get any completion
    }
  }
})

🙁 Actual behavior

We can't get any completion for object literal shorthand in setup return.

🙂 Expected behavior

Like common object literal shorthand.

Ref: #41259 #41539
From: vuejs/vetur#2544

[andrewbranch]

It’s because setup gets a contextual return type of Promise<RawBindings> | RawBindings | RenderFunction | void from defineComponent. RawBindings is actually inferred from that position itself, so it doesn’t contribute, but the Promise itself is contributing:

We should probably carve out a rule to not give object literal member completions for members of the global Promise type, which might be enough to fix this one... but in general, these shorthand property completions aren’t going to work anywhere there’s a contextual type.

[Zenthae]

any news on this ?

[Andarist]

these shorthand property completions aren’t going to work anywhere there’s a contextual type.

Couldn't those things be concatenated with contextual type members being prioritized?