microsoft / microsoft/TypeScript
Generic not inferred inside mapped type parameter
Open
Nobody has claimed this yet.
Bug
Domain: check: Type Inference
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
TypeScript Version: 3.2.2
Search Terms: generic inference {} createStructuredSelector mapped types
Code
type Selector<S, R> = (state: S) => R;
declare function createStructuredSelector<S, T>(
selectors: { [K in keyof T]: Selector<S, T[K]> },
): Selector<S, T>;
type State = { foo: number };
declare const mySelector: Selector<State, boolean>;
// Workaround: use explicit generics
// const result = createStructuredSelector<State, { mySelector: boolean }>({
// `State` generic incorrectly inferred as `{}`.
const result = createStructuredSelector({
// Unexpected type error under `strictFunctionTypes` due to bad inference (above)
mySelector,
});
result;
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the TypeScript 3.2.2 example with the mapped type and strictFunctionTypes enabled, then trace the generic inference behavior for createStructuredSelector. Done means the unannotated call infers State instead of {} and no longer produces the reported type error; no source file or test path is named in the issue.
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
- Clearly specified
- Newbie friendliness
- 35/100