microsoft / microsoft/TypeScript

Provide metadata about TypeScript's available refactorings and quick fixes

Offen
#34,859 4 Kommentare 2 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@orta arbeitet bereits daran.

Seit 07.11.2019.

Committed Rescheduled Suggestion
Vorherrschende Sprache
Go
Sterne
111k
Forks
14.3k
Ø Merge
1 T. 19 Std.
Gemergte PRs (30 T.)
117

Beschreibung

Problem

We are working on improving discoverability of JS/TS refactorings and quick fixes in VS Code. As part of this, we'd like to put together documentation and a new contribution points that lists out the code actions provided by TypeScript

At the moment, the only way I know to determine this list is to look through the TypeScript codebase.

Proposal

We'd like a way to get metadata about all the current TS quick fixes and code actions. The main information we are interested in:

  • Identifier for the quick fix
  • Human readable name / description for the quick fix
  • (possibly) A way to map this description to the localized description that TS ships with

Two ideas on how this could be exposed:

  • In the TS repo, check in a generated CodeActions.json file. This file would be updated whenever the refactorings or quick fixes change. VS Code would not need this to be published as part of the TypeScript package

  • Expose a command line option or tool to dump out all known refactorings and quick fixes.

/cc @orta Ryan mentioned you may also find this useful for the website

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.