microsoft / microsoft/TypeScript
Fix/fix all to remove TS-specific constructs in JS files
Open
Nobody has claimed this yet.
Domain: LS: Quick Fixes
Effort: Moderate
Help Wanted
Needs Proposal
Suggestion
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
Today in a JS file, if you write something like
function foo(x: string) {
}
Type annotations can only be used in TypeScript files.
We should provide a quick fix for these
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
The issue names no files or tests. Start by locating the diagnostic and quick-fix path for “Type annotations can only be used in TypeScript files,” then determine which TypeScript-specific constructs and fix-all coverage are in scope. Done means the relevant JavaScript diagnostics offer both a quick fix and fix-all.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100