rust-lang / rust-lang/rust-analyzer
Support untrusted workspaces in VSCode
Open
Nobody has claimed this yet.
A-vscode
C-feature
S-unactionable
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
We could potentially disable proc macros if not given trust, for example.
See https://github.com/microsoft/vscode/issues/120251 for API details.
(from https://twitter.com/ekuber/status/1403499878836322311)
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 issue 120251 for the workspace-trust API details, then determine how untrusted workspaces should affect proc macros in rust-analyzer. Done means the supported behavior is defined and implemented for untrusted workspaces, with verification that trusted-workspace behavior remains appropriate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, vscode
- Domain
- devtools, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100