rust-lang / rust-lang/rust-analyzer
Consider marking disabled code actions
Open
Nobody has claimed this yet.
A-assists
S-actionable
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
We may want to do this to increase visibility into our capabilities: https://code.visualstudio.com/updates/v1_41#_codeactiondisabled
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked VS Code CodeActionDisabled documentation. The issue names no file, test, or entry point; investigate rust-analyzer's code-action and LSP handling, and define completion as disabled actions being surfaced consistently with the referenced behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100