Create folder when adding folder to workspace

[DeadlySurgeon]

When in a workspace, and you right click and select "Add Folder to Workspace", the drop down to select a folder has no way to create folders, so you have to create it first outside of code-server, usually by using the terminal. While it really isn't too much of an issue to drop down into a terminal and just run mkdir <path>, it would be nice to have some kind of way to create folders as you're adding them, as does regular VSCode since it opens up a File Browser Dialog native to the OS. Maybe a file browser component should be created and added to help with navigation and file management, or the existing "Add Folder to Workspace" just needs to be tweeked?

[jsjoeio]

Hmm...to make sure we fully understand what you mean, do you mind posting a video showing it working in VS Code and also a video showing how it currently works in code-server? That would help a lot.

[DeadlySurgeon]

I can later this week, yeah.

[DeadlySurgeon]

I know I said later this week, but life hit me like a truck.

So with my instance, I don't have the folder ~/rust. When I type out /home/surgeon/rust and press enter, instead of creating this directory, it will complain that it doesn't exist. To create this directory on the remote instance, I'll need to go into a terminal to run mkdir on it. What if it instead had a dialog that said something on the lines of The path ${path} doesn't exist, would you like to create it [ yes | no ], and if possible, where ${path} is the parts of the directory that exist would be in green while the parts that don't would be in red so you know what folders it would be creating:

Color Example

(obviously there would be a button or something in place of [ yes | no ]

On a side note, potentially pressing enter again would create it, so those who are used to only using keyboard shortcuts could continue only using keyboards in this flow, and esc would cancel it like it does now.

[jsjoeio]

OH! Okay, now I understand what you mean. That would be great! Thanks for explaining that :)

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no activity occurs in the next 5 days.