Code actions contribution point

Problem

For feature requests such as #52846 or any improved refactoring UX, VS Code needs to know all the code actions that are available for a language. Some information about available code actions is provided by CodeActionProviderMetadata but only if an extension has been activated and the provider has been registered

Proposal

To support this, we likely want a new contribution point that lets extensions statically tell us about the general classes of the code actions that they provide:

{
  "contributions": {
    "codeActions": [
      {
        "languages": [
          "javascript",
          "javascriptreact",
          "typescript",
          "typescriptreact"
        ],
        "actions": [
          {
            "kind": "refactor.extract.constant",
            "title": "Extract constant",
            "description": "Extract expression to a constant."
          }
        ]
      }
    ]
  }
}

Potential use cases for this info

• Show on the extension’s contribution page #84091
• IntelliSense for codeActionsOnSave (c8d64b13e5585476bedcb0b34314329c2d75d88b)
• IntelliSense for configuring refactors in the keybinding json editor #84033
• IntelliSense for configuring refactors in UI keybinding editor #84072
• Improving the refactor context menu in VS Code

/cc @kieferrm

[mjbvz]

This proposal does not effect the existing CodeActionProvider api (which lets your extension control which actual code actions are shown to the user in the editor). The static contribution point proposed here aims to supports some of the use cases outlined above without needing to activate any extensions

[heejaechang]

Pylance team wants to expose all individuals fix all code actions to users so they can configure which fix all code actions run on file save. currently there seems no way to add those individual action names in editor.codeActionsOnSave schema. and no way to provide default value for code actions on save for each fix all code actions.

I think that makes it very hard for users to discover each fix all actions and make default such as source.fixAll: true very intrusive since updating extension without knowing that it just added new fix all code action can change users code unexpectedly. furthermore, in current design, it will be very hard to find out which extension actually did it.

Please, provide a way to configure this by each fix all code action provider