rust-lang / rust-lang/rust-analyzer
Extension activates in empty directories
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
I was going to try your suggestion of copying files into a new directory until the extension was triggered and found out that it is triggering immediately, even when opening an empty directory. I tried this a couple of different ways (see below) with the same results.
In all test cases I followed these steps:
- Close the current workspace or folder from the
Filemenu. - Close VS Code application.
Then either, Right-click the empty folder and select Open with Code, or,
- Launch Code form the Start menu.
- Open the empty directory from
File | Open Folder...menu.
Originally posted by @damianpowell in https://github.com/rust-analyzer/rust-analyzer.github.io/issues/204#issuecomment-1564005303
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
Reproduce the activation behavior using the listed empty-folder workflows in VS Code, first closing the workspace and application as described. No source file or test is identified in the issue, so locate the extension activation entry point and existing activation tests. Done means the extension does not activate when an empty directory is opened, while its intended activation behavior remains covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, vscode
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100