File Nesting: Allow `<directory>/<file>` patterns in Value column

[dannymcgee]

In Rust, modules follow a prescribed directory structure that follows one of two patterns:

├── my
│   ├── inaccessible.rs
│   ├── mod.rs   <-- the "root" of the `my` module
│   └── nested.rs
├── lib.rs
└── split.rs

OR (the newer and now recommended option)

├── my   <-- children of the `my` module are nested in this directory
│   ├── inaccessible.rs
│   └── nested.rs
├── lib.rs
├── my.rs   <-- the "root" of the `my` module
└── split.rs

I'd like to configure VS Code to reflect the module structure in the Explorer tree by displaying something like this:

├── lib.rs
├── my.rs
│   ├── inaccessible.rs
│   └── nested.rs
└── split.rs

To that end, I tried adding the following File Nesting pattern to my settings.json:

{
  // ...
  "explorer.fileNesting.patterns": {
    // ...
    "*.rs": "${capture}/*.rs",
  }
}

But the Explorer tree still shows my <module-name> directory and <module-name>.rs file as separate, sibling entries in the tree, instead of nesting the children of the <module-name> directory under the <module-name>.rs file.

[vs-code-engineering]

Thanks for creating this issue!

However, as the description is not in English, it is hard for us to work on it. If you are able to, please edit this issue to be in English. Please do not add a new comment or create a new issue, but rather edit the existing issue.

Unfortunately, automatic translation services are not able to handle the technical language needed to effectively communicate about software issues, so we recommend finding a human translator who is familiar with our technology to help translate.

Otherwise, this issue has been marked as needing translation and a community member may be able to help translate it.