You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Provide metadata about TypeScript's available refactorings and quick fixes #34859
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 Therox (@orta) Ryan mentioned you may also find this useful for the website
Looks like there's no changes on VSCode side yet, punting to 4.x - will also try think about whether this info could get into the website now it's close to wrapping
Activity
mjbvz commentedon Nov 6, 2019
Here's how we plan on using this information on the VS Code side: microsoft/vscode#82718
orta commentedon Nov 7, 2019
Ah! Great - linking to microsoft/TypeScript-Website#48 - I can grab you this in a structured way so that I can use it for the site
orta commentedon Nov 7, 2019
OK cool, looks like I can extract most of the things you want https://gist.github.com/orta/3f56c1aec87a419d2b4a2a542f1f0d5b - WIP branch
orta commentedon Apr 14, 2020
Looks like there's no changes on VSCode side yet, punting to 4.x - will also try think about whether this info could get into the website now it's close to wrapping
13 remaining items