microsoft / microsoft/TypeScript

"Infer types from usage" not consider js object initializer

Open
#37,099 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Experience Enhancement Suggestion
Dominant language
Go
Stars
111k
Forks
14.3k
Avg merge
2d 4h
Merged PRs (30d)
132

Description

TypeScript Version: Nightly
Search Terms: infer types from usage
Code

function foo(/*infer parameters from usage 'here'*/x) {
	let obj1: { a: string } = { a: '' }
	obj1.a = x;
	let obj2: { a: boolean } = { a: true };
	obj2.a = x;
	bar({ a: x });
}

function bar(obj: { a: object }) {
}

Expected behavior:
foo become to foo(x: string|boolean|object)
Actual behavior:
foo become to foo(x: string|boolean)
Playground Link: Playground

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 the inferred type of foo with the expected signature. Trace how usage inference handles obj1.a = x, obj2.a = x, and bar({ a: x }); the fix is complete when the object-literal usage contributes object to the inferred union.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
compilers
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.