microsoft / microsoft/TypeScript
Deprecated should support contextual type with signature resolution
Open
Nobody has claimed this yet.
Effort: Moderate
Experience Enhancement
Help Wanted
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
TypeScript Version: 3.7.x-dev.201xxxxx
Search Terms:
Code
// A *self-contained* demonstration of the problem follows...
// Test this by running `tsc` on the command-line, rather than through another build tool such as Gulp, Webpack, etc.
declare function h(v: (a: string) => void)
declare function vv (): void
/** @deprecated */
declare function vv (v: string): void
declare function vv (v?: string): void
h([|vv|])
Expected behavior:
vvs is deprecated.
Actual behavior:
nothing.
Playground Link:
Related Issues:
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 running the self-contained TypeScript snippet with tsc and confirm that the deprecated overload is not reported. Investigate contextual typing and signature resolution for the function passed to h; done means the deprecated vv signature is recognized and the expected diagnostic appears.
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
- 38/100