Poor autocomplete inside object literal as the return value of a getter

[whzx5byb]

🔎 Search Terms

object literal getter completion

🕗 Version & Regression Information

• This is the behavior in every version I tried

⏯ Playground Link

https://www.typescriptlang.org/play/?ts=5.5.0-beta#code/JYOwLgpgTgZghgYwgAgILIN7IFDOTAewIAoBKALk2QAcoDrowBPAOTgFsJKQBXdgI2jIAvgG5cyfnCiUsteo1YcuyXgKFjsw7NgQEQAZzDI4ldAF5MEvIRKkqUCGB5QQVvB48B6L8gA8ALTIYFBMwUzUoADmyABE1LHIABbQENYewjiewgA0Op5RTpLSZO6eyI7OrlTpnj7+QSFhzJEgMfGJKY61IunawkA

💻 Code

interface A { 
  foo(): { propertyName: number };
  bar: { propertyName: number };
}

const a: A = {
    foo() { return {
        // <- try typing "p" here
      } 
    },

    get bar() {
      return { 
        // <- try typing "p" here
      }
    }
}

🙁 Actual behavior

😊 Good completions inside the function body:

😢 Poor completions inside the getter body:

🙂 Expected behavior

It should provide the same completions inside a getter, as it does inside a function.

Additional information about the issue

No response

[Andarist]

Those completions are computed based on the contextual type and it seems that return types of getters are not contextually-typed here:

interface Test1 {
  foo: (arg: number) => void;
}

const t1: Test1 = {
  get foo() {
    // Parameter 'arg' implicitly has an 'any' type.(7006)
    return (arg) => {};
  },
};

interface Test2 {
  bar: [string]
}

const t2: Test2 = {
  get bar() {
    // Type 'string[]' is not assignable to type '[string]'.
    //   Target requires 1 element(s) but source may have fewer.(2322)
    return ['']
  },
};