LSP Refactoring Capabilities

[Mateusz Kadlubowski (xeho91)]

What Am I Proposing?

Add refactoring code actions to the typescript@7 LSP.

Why?

Modern IDEs (such as VS Code, Neovim, and Zed) rely on refactoring code actions as a core part of the TypeScript editing experience.
Without these refactoring actions, the typescript@7 LSP feels incomplete compared to vtsls / typescript-language-server.
Users migrating to this newer version lose these workflows.

Refactoring Actions

Verified against VS Code TypeScript refactoring docs and TypeScript source.

Umbrella PR with adding framework for refactoring capabilities: #4855

• (1) Add/remove braces from arrow function source
• (2) Convert between arrow function and function expression source
• (3) Convert between default export and named export source
• (4) Convert between named imports and namespace imports source
• (5) Convert between string and template literal source
• (6) Convert overload list to single signature source
• (7) Convert to optional chain expression source
• (8) Convert parameters to destructured object source
  • ⚠️ Likely won't be ported Port Convert parameters to destructed object refactoring #2281
• (9) Extract function source
• (10) Extract type source
  • Port Extract type refactoring capability xeho91/typescript-go#2
• (11) Extract variable source
• (12) Generate get and set accessors source
• (13) Infer function return type source
  • Port Infer function return type refactoring capability xeho91/typescript-go#1
• (14) Inline variable source
• (15) Move to new file source
  • Interactive code actions (like "Move to file") #2468