microsoft / microsoft/TypeScript

Function expression or method is not inferable when we have mapped type with a conditional type

Open
#60,047 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Domain: check: Type Inference Help Wanted Possible Improvement
Dominant language
Go
Stars
111k
Forks
14.3k
Avg merge
2d 4h
Merged PRs (30d)
132

Description

🔎 Search Terms

conditional method arrow function

🕗 Version & Regression Information
  • This is the behavior in every version I tried, and I reviewed the FAQ
⏯ Playground Link

Playground Link

💻 Code
type Map<T> =  { 
  readonly [P in keyof T]: T[P] extends boolean ? "boolean":  "other"
} 
export function buildCommand<F extends Record<string, unknown>>(builderArgs: { 
  func: (p: F) => void
  params: Map<NoInfer<F>>
}) {

}
type Foo = { foo: boolean };
// Function expression does not work
buildCommand({
  func: function (p: Foo) { },
  params: {
    foo: "boolean"
  }
})

// Methods don't work
buildCommand({
  func(p: Foo) { },
  params: {
    foo: "boolean"
  }
})

// Arrow function works
buildCommand({
  func: (p: Foo) => { },
  params: {
    foo: "boolean"
  }
})
🙁 Actual behavior

For the first two calls we get an error while the third one is successful

🙂 Expected behavior

All three calls should be successful

Additional information about the issue

Removing the constraint from F (Playground Link) or changing it to F extends Record<keyof F, unknown> (Playground Link) will remove the error.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked TypeScript Playground reproduction and compare inference for the function expression, method, and arrow-function cases under the Record<string, unknown> constraint. Done means all three buildCommand calls are accepted while preserving the reported behavior when the constraint is removed or changed.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
compilers
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.