Open ematipico opened 3 weeks ago
Is #1274 a candidate for an assist? It doesn't feel like a lint rule, but editing strings is beyond the scope of a formatter.
I think it could be a good candidate for assist, yes!
I think it could be a good candidate for assist, yes!
Cool. I just wanted to make sure I understood what this was. Have a nice day!
As discussed on Discord, an attribute sorter for typescript interfaces would be a nice addition to the sorting LSPs.
Description
Issue to track a new feature called Analyzer assists (or actions).
Assists (code actions)
Assists/Action are a concept of the LSP spect. Code actions are usually opt-in, and the user can decide to apply these actions using the UI of a client.
Assists are code actions that can be categorized as refactor opportunities, extractions, etc.
We will borrow this concept and make ours inside the Biome LSP, and we will provide a way to enforce it in the CLI.
Possible configuration:
Assists can be opted in from the LSP too. For example, a LSP client can send the following code to enable
useSortKeys
from the previous example, in VSCode:Or, using zed:
Example of assists:
Why not lint rules?
The goal of the Biome linter is to catch possible bugs, enforce some idiomatic coding pattern, or propose some conventions. The Biome linter isn't meant to enforce stylistic decision, because that's what the Biome formatter is meant for.
Why not a formatter?
The Biome formatter is meant to enforce a coding style that matches Prettier as much as possible, and to reduce the diffing inside the PRs. An assists like sorting could have a huge impact on the diffing of PR, that's why assists aren't meant for a formatter.