Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Single nested file in folder is revealed even though "explorer.autoReveal": false setting #168791

Closed
henrikvilhelmberglund opened this issue Dec 11, 2022 · 1 comment
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@henrikvilhelmberglund
Copy link

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version: 1.74.0
  • OS Version: Win10 64bit

Single nested file in folder is revealed even though "explorer.autoReveal": false setting.

Here is a gif:
nested

My pattern is

"explorer.fileNesting.patterns": {
    "+page.svelte": "${basename}.js, ${basename}.server.js",
    "+layout.svelte": "${basename}.js, ${basename}.server.js"
  },

settings are

  "explorer.fileNesting.enabled": true,
  "explorer.fileNesting.expand": false,
  "explorer.autoReveal": false

Steps to Reproduce:

  1. Open an empty folder.

  2. Create a folder.

  3. In the folder, create +page.svelte

  4. In the folder, create +page.js

  5. Close the nesting on +page.svelte by clicking the arrow.

  6. Close the folder.

  7. Open the folder.

  8. The folder is opened with +page.svelte and +page.js autorevealed.
    Expected: The folder is opened with only +page.svelte visible.

  9. In the folder, create a new folder.

  10. Close the nesting on +page.svelte by clicking the arrow.

  11. Close the top folder.

  12. Open the top folder.

  13. The folder is opened with only +page.svelte visible and the newly created folder visible.

So, this works as expected with nested files which have folder or file siblings but not when they are the only files in a folder.

@lramos15
Copy link
Member

\duplicate #149084

@lramos15 lramos15 closed this as not planned Won't fix, can't repro, duplicate, stale Dec 12, 2022
@VSCodeTriageBot VSCodeTriageBot added the *duplicate Issue identified as a duplicate of another issue(s) label Dec 12, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Jan 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

3 participants