NoInfer breaks discriminate union autocomplete

🔎 Search Terms

no infer discriminate union

🕗 Version & Regression Information

Tested on version 5.6.3

⏯ Playground Link

https://www.typescriptlang.org/play/?#code/JYOwLgpgTgZghgYwgAgILIN4ChnLATwAcIAuZAcjnIBodkA3OAGwFdTkBnMKUAcwG4sAXyxZQkWIhQAhTHQLEy5AEY06HYAC92IFgFtl0QSKwKUAVRDAA9iGQBeNMgA+yaYKwwWIBGBt3EJEIwAB4AFWQIAA9IEAATDmRLfwA+AApvfzIAOWsASRAYaHCUgEo5YVFAiGC0jDMlKiFSoA

💻 Code

interface A {
  type: 'a',
  value: string;
}

interface B {
  type: 'b',
  size: number;
}

type Union = A | B;

function accept<T extends Union>(union: NoInfer<T>) {

}

accept({type: 'a'})

🙁 Actual behavior

When trying to autocomplete after writing type a the autocomplete doesn't work (but the result does get type checked):

🙂 Expected behavior

Even with NoInfer it should autocomplete the other properties of the "inferred" discriminate union case as it correctly type checks it if written wrong.

Additional information about the issue

No response

Start with the linked TypeScript Playground reproduction and compare autocomplete behavior with the existing type-checking result for NoInfer and a discriminated union. Done means the remaining properties of the selected union case are offered after entering type 'a', while incorrect values continue to be rejected.