"Reveal in Explorer View" fails for nested files

[OldStarchy]

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

• VS Code Version: 1.70.0-insider (user setup)
• Commit: 9cf2fab
• OS Version: Windows_NT x64 10.0.22000

Steps to Reproduce:

1. Enable file nesting "explorer.fileNesting.enabled": true
2. Create two files, foo.js and foo.min.js
3. With the foo.min.js editor tab open the "Reveal in Explorer View" command
4. The foo.min.js file is not revealed in the explorer view

Once you manually expand the foo.js nesting to reveal foo.min.js the command will start working, even if you collapse the tree under foo.js again.

It will stop working again if any change to the tree view is made (creating, deleting, or renaming a file) while the nested tree is collapsed.

Maybe related: #155766

[lramos15]

This is most likely caused by the tree being async. It does not know that node exists because it has not been resolved yet. You having the file open is not a guarantee that the file is in the explorer (think outside files).

[kredenac]

Nested files option in VS code is great to automatically declutter explorer view, but this bug is extremely annoying.
When you open some file, VS code automatically shows its location in explorer view, so that you can orient yourself and see what are neighboring files.
This prevents that sync from happening, and this slowdown forces the decision to stop using nested files until it's fixed.