Allow/use folder name when opening file in multi-root workspace
See original GitHub issueContext
We have a mono-repo with multiple Dart code projects which are each in their own folder directly under the root.
For optimal tooling support we use a “multi-root workspace”.
The file structure looks like this:
/
a/
foo.txt
b/
bar.txt
The Problem
Trying to open a/foo.txt
from the quick open menu (<kbd>CMD</kbd> + <kbd>P</kbd>) leads to 0 results.
Feature Request
Tooling in the CLI as well as the paths in PRs on GitHub often reference the “local” paths inside the repository, e.g. a/foo.txt
which also maps 100% with the file layout in the VS Code explorer.
Unfortunately when pasting a/foo.txt
into the file open (<kbd>CMD</kbd> + <kbd>P</kbd>) dialog, it doesn’t show any results. When using just foo.txt
the correct file in a/
is offered.
I think it would be nice to have these “perfect matches” offered to open directly.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:6 (4 by maintainers)
Top GitHub Comments
I believe the underlying issue is that we take the user typed query string from quick open and run it over all folders that are known to the multi root workspace. We would probably have to detect that the user has put the name of a root workspace and remove that from the search string? Or maybe we could trick Ripgrep into understanding that a root workspace has a certain prefix (name) that should be taken into account?
Actually isn’t this https://github.com/microsoft/vscode/issues/32444 ?