Improve the UI/UX of the Multi-Root Workspace Project Outline Pane
See original GitHub issueThis is just a slight UI/UX improvement request.
Brief Issue Summary
I’m using a multi-root workspace SSH’d into a remote VM. The CMake Project Outline pane shows full paths even though they all start with the same string - /home/vagrant/mercury
. Here’s what it looks like:
Expected:
If all the multi-root workspace paths start with the same prefix (EG: /home/vagrant/mercury
), then get rid of that prefix. This would make the pane easier to read.
Apparent Behavior:
N/A
CMake Tools Log
N/A
Developer Tools Log
N/A
Platform and Versions
- Operating System: Win10 VSCode SSH-Remoted into an Ubuntu 20.04 VM
- CMake Version: 3.16.3
- VSCode Version: 1.46.1
- CMake Tools Extension Version: 1.4.1
- Compiler/Toolchain: Several. Hence the multi-root workspace.
Other Notes/Information
N/A
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (3 by maintainers)
Top Results From Across the Web
Multi-root Workspaces in Visual Studio Code
You can open and work on multiple project folders in Visual Studio Code with multi-root workspaces.
Read more >Visual Studio Code tips for monorepo development with Multi ...
A multi-root workspace is a feature in Visual Studio Code where you can have multiple root folders in one explorer view.
Read more >A Guide to Monorepos for Front-end Code - Toptal
A monorepo or monorepository is a code management and architectural concept whereby you keep all your isolated bits of code inside one super...
Read more >What is a 'workspace' in Visual Studio Code? - Stack Overflow
When opening a multi-root workspace things behave differently. Firstly, the WORKSPACE SETTINGS tab shows the options set in the .code-workspace file. Secondly, ...
Read more >Projects in an Altium 365 Workspace | User Manual
This page looks at working with projects through the Altium 365 Workspace's browser interface, including creation, upload, editing, sharing, cloning, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Can you point out the 3rd request? I’m only seeing two:
Maybe the 3rd one was from your first post, though I’m thinking the setting you proposed in the follow up would replace that. It’s possible that this setting could even allow you to customize the node any way you like with a few supported variables. See
window.title
for an example of what I’m thinking (but not committing to yet! 😄) though we’d have different variables, of course:Quick follow-up. It’d be great to have more control over how the Project Outline pane appears. For a multi-root workspace, maybe there could be a setting like
cmake.projectOutline.multiRootOutline.sectionFormat
that could have a few common-sense settings. For example, being able to have the top level sections just be the “names” of the multi-root folders instead of the paths. Etc.Another thought I had was having an option like
cmake.projectOutline.showEmptyProjects
that could betrue
orfalse
. I have a few dummy empty projects I’m using until https://github.com/microsoft/vscode-cmake-tools/issues/1069 gets fixed, so it’d be great to be able to just hide them. But I’m sure there are other cases where people use empty projects for their own special reasons, and don’t need to see them in the Project Outline pane.Just a couple thoughts. Let me know if these should be broken out into separate issues. I renamed this issue to
Improve the UI/UX of the Multi-Root Workspace Project Outline Pane
to encompass these three requests.