microsoft / microsoft/TypeScript
Add a refactoring that annotates an implicit or explicit any with a best guess type inferred from its use sites
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
I would very much appreciate having a codefix (refactoring) that, given an explicit any annotation, offers to change it to an {} annotation.
For example, given
function log(x: any) {
console.log(x);
}
a code fix would be offered to change the declared type of x to {} resulting in
function log(x: {}) {
console.log(x);
}
However, given
function log(x: any) {
console.log(x.name);
}
a code fix would be offered to change the declared type of x to { name: any } resulting in
function log(x: {name: any}) {
console.log(x);
}
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 with TypeScript's codefix/refactoring entry point and review the explicit and implicit any examples in the issue. Define the supported use-site inference cases and expected replacement types, then add focused tests showing that the refactoring is offered and produces the requested annotations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100