Microsoft/TypeScript

Fix/fix all to remove TS-specific constructs in JS files

Open

#40,599 opened on Sep 16, 2020

View on GitHubContributor guide
 (3 comments) (1 reaction) (0 assignees)TypeScript (13,395 forks)batch import
Domain: LS: Quick FixesEffort: ModerateHelp WantedNeeds ProposalSuggestion

Repository metrics

Stars
 (108,860 stars)
PR merge metrics
 (Avg merge 6d 17h) (9 merged PRs in 30d)

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

Research direction
Investigate the TypeScript compiler's error handling for type annotations in JavaScript files. Look at how existing quick fixes are implemented and follow that pattern to create a new quick fix for removing TypeScript specific constructs.
Tech stack
typescriptjavascript
Domain
compilers
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitTypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65