🐛 Biome LSP does not announce the quickfix.suppressRule code action to a client

[vitallium]

Environment information

CLI:
  Version:                      1.9.2
  Color support:                true

Platform:
  CPU Architecture:             aarch64
  OS:                           macos

Environment:
  BIOME_LOG_PATH:               unset
  BIOME_LOG_PREFIX_NAME:        unset
  BIOME_CONFIG_PATH:            unset
  NO_COLOR:                     unset
  TERM:                         "xterm-256color"
  JS_RUNTIME_VERSION:           "v20.17.0"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         unset

Biome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    false
  VCS disabled:                 false

Workspace:
  Open Documents:               0

What happened?

1. When Biome LSP sends its capabilities back to the client, it doesn't send the quickfix.suppressRule code action among the default code actions: quickfix.biome, source.fixAll.biome and source.organizeImports.biome`.
2. Without that capability the client does not know that this code action is available on the server side.

How to reproduce:

1. Install the Zed editor and the Biome extension
2. Create a simple Typescript file with the following content:

let hello;

3. You should see the reported linting error from Biome LSP, but if you click on the available code actions, the quickfix.suppressRule option will be missing.

See also microsoft/vscode-eslint#1905 (comment)

Thanks! Let me know if you need anything else.

Expected result

The Biome LSP should send all possible code actions to a client to ensure that:

1. The client knows about possible code actions
2. The client does not send an invalid code action to a server.

Code of Conduct

• I agree to follow Biome's Code of Conduct

[ematipico]

Not a bug, because we don't handle that yet.

PRs are welcome

[vitallium]

Not a bug, because we don't handle that yet.

PRs are welcome

@ematipico Hi, thanks for the quick reply! I’m happy to contribute, but I’d like to know if you have anything specific in mind for the implementation, or should I just send a PR and we can iterate from there? Thanks again.