Virtual Documents based dependency source reader lost the in-editor breadcrum

[spangaer]

Describe the bug

Before using the virtual documents back-end for showing dependency source files the breadcrum navigation was available in the editor like for any other project source file.

Possibly this was due to it just being a copied source file, so it came "for free" before and now no longer is, but it does feel like a regression.

• there in ext v1.11.1 + metals 0.11.0
• there in ext v1.12.0 + metals 0.11.1
• not there in ext v1.13.0 + metals 0.11.2 (didn't test with the flag to turn virtual documents off)

Expected behavior

No response

Operating system

Windows

Editor/Extension

VS Code

Version of Metals

v0.11.2

Extra context or search terms

No response

[kpodsiad]

Possibly this was due to it just being a copied source file, so it came "for free" before and now no longer is but it does feel like a regression.

Yes, this is exactly what happened. As a workaround, for now, you could use Metals: Reveal Active File in Side Bar described in the release notes. It's not perfect but should be helpful in some situations.

[Arthurm1]

@olafurpg has suggested FileSystemProvider support which would allow proper exploration of the jars in the file explorer view (and bring back breadcrumbs) and seems fairly straightforward.

[spangaer]

Is it delusional to think that would automagically bring the ability to browse JARs for resources genre .conf files, because that would really be supercool!