Description

interface T {
    <T>(input: { type: 'text' })
    <T>(input: { type: 'json' })
    <T>(input: { type: 'buffer' })
}

declare const func: T

func({ type: /**/ })

Contributor guide

Tech stack

typescript

Domain

developer experiencetooling

Issue type

bug

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

half day

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

stale

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

clear

Prerequisites

understanding of TypeScript overloadsfamiliarity with language service completion logic

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

35

Research direction

Examine the TypeScript language service completion logic in `src/services/completions.ts` and related files. Focus on how completions are generated for function calls with overloads, especially when arguments are object literals. The playground link (https://www.typescriptlang.org/play?noImplicitAny=false&ts=5.0.0 dev.20230208#code/...) reproduces the issue. The code shows an `interface T` with multiple overloads returning generic `<T>` and a `func` call with an object literal. Note that completions work when `<T>` is removed. This is similar to issue #51047, which may be the root cause. Investigate how the presence of generic type parameters in overloads affects completion in the context of object literal arguments.