Compact folder rendering looks weird

[jrieken]

re #85928

IMO we had a much better in-between solution using chevrons or no spacing. To me the slash and the spacing look like screen cheese.

[jrieken]

Proposal: Use normal character spacing and opacity

[joaomoreno]

Closing this for now and waiting for more user feedback.

[gabeklein]

Personally I'd like to see an option to make nested folders less prominent (lighter, less opacity). Reason being that usually the root folder is the relevant, most "unique" folder and should be visually more prominent.

[gjsjohnmurray]

@gabeklein by "the root folder" do you mean the leftmost one on the sequence? In other words, you'd like the opposite of what @jrieken proposed in his screenshot here?

[gabeklein]

@gjsjohnmurray

Yep, basically I tend to work with a mono-repo and have a good number of packages (in my node projects) I'll tend to use files.exclude to make only items in /src visible and togglable to get a "Zen"-like experience in my explorer.

This is what it looks like with compact folders active. Not the easiest to scan quickly while hopping between modules. ⬇ And here this is without.

Since the package's root folder is the most relevant thing to me personally, having /src be less prominent would help me comfortably scan a large number of packages like this while still enjoying the benefits of compact mode.

If I had a way to explicitly set the opacity of /src ect... I'd make it close to zero, resulting in the second image just without the extra line for subfolder. It'd make my development experience a lot more comfortable.

Just my personal take on this issue. 🙂 Thanks for responding

[joaomoreno]

If I had a way to explicitly set the opacity of /src ect... I'd make it close to zero, resulting in the second image just without the extra line for subfolder. It'd make my development experience a lot more comfortable.

What if you had the possibility of letting the explorer know that express and interface and webpack should not be folded up?

[gabeklein]

@joaomoreno Sorry I don't really follow, could you explain?

[joaomoreno]

I mean: a workspace setting that you could mark certain folders never to be folded up. I believe your argument has something to do with the lib/* folders, and not just any folder, being folded up with a single child.

So we could offer a setting, e.g. explorer.preventCompactFolder which would have a glob pattern value, eg. lib/*, and the explorer wouldn't render those folders as compact, even if they only have a single child.