rust-lang / rust-lang/rust-analyzer
vscode: contributed explorer file nesting pattern overrides defaults
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
the change for #13580 doesn't add a file nesting pattern but overrides the whole list of patterns vscode provides by default. this means that with the rust-analyzer extension installed, vscode won't nest package.json and package-lock.json unless i configure them to again.
while i agree with the idea behind #13580 it doesn't currently seem possible for extensions to contribute additional nesting patterns. i've opened microsoft/vscode#168498 for that
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 reviewing the change for #13580 and the linked VS Code issue microsoft/vscode#168498 to understand the nesting-pattern contribution limitation. Confirm whether the upstream limitation has changed; done means contributed patterns no longer replace VS Code's default nesting patterns, including package.json and package-lock.json.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, vscode
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100