Repository navigation
No object literal completions for type parameter constrained to mapped type #16136
Description
Isolated from this StackOverflow issue
interface Foo {
foo(): void;
}
declare function f<T extends Partial<Foo>>(x: T): T;
f({
/*$*/
})Request completions at the cursor in the above sample.
Expected: foo is a completion.
Actual: No completions.
Activity
[-]No object literal completions for object constrained to mapped type[/-][+]No object literal completions for type parameter constrained to mapped type[/+]DanielRosenwasser commentedon Sep 19, 2017
I believe that this is because
{}fulfills the constraint so that we end up with an inference forTwhich causes us to give completions from{}instead of the constraint ofT.DanielRosenwasser commentedon Jul 25, 2025
Seems to work now - I feel like Andrew Branch (@andrewbranch) might have fixed this?