-
-
Notifications
You must be signed in to change notification settings - Fork 223
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE] - Suggest to open .code-workspace
when opening projects that contains workspaces in its root
#617
Comments
I have found that editing the project.json file and providing the folder and the name of the ".code-workspace" file name in the "rootPath" works well. But this does not seem to be covered in the documentation. I did not find any documentation for the project.json "Paths" setting either. |
Thanks for the heads up, @D35. Unfortunately, I'm not using the manual |
@D35 , thanks for helping, but @wottpal scenario is a bit different. He wants VS Code to suggest opening the BTW, the support to If you think the documentation could be improved somehow, please open a new issue or add some comments to #394, which was opened requesting a I’m also planning a Hope this helps |
I just hit this issue and was about to make a feature request to open workspace if a .code-workspace is present, else open folder (as is the current default.) When opening a project from my favorites of this extension, I currently see the following message: I'd like for it to just open the workspace directly and not ask me (I'm assuming this message is a vscode (proper) message.) The great thing about workspaces is that any previously opened files, either saved or unsaved, are opened as well and our files/folder tree is in a state where we left it. With that, we're able to continue from where we left off with ease. Opening a folder, on the other hand, has no history. Anyway, I didn't see this option in the extensions Settings when I check for one, but I'll take a look at the readme and see if I can get it to use the workspace instead. ETA Okay, according to the readme, if you open a workspace and Save Project it will save it as a workspace. If you open the project as a folder, it will save it as a folder. I opened the project using the list of git repos, the ones that are listed in this extension below favorites and that's how I ended up having a folder open and not a workspace (not how I would normally open a project, but I was using the extension.) Anyway, I guess that would be a different features request i.e. open git repos as workspace if project has a .code.workspace file or if is a project that has a rootPath that points to a .code.workspace, else open as folder. |
Hey @Natetronn, as I had the exact same need, I developed a small plugin to do exactly this: https://marketplace.visualstudio.com/items?itemName=zoma.vscode-auto-open-workspace Please also see this discussion for reference. |
@wottpal thanks for sharing! I gave it a try on two projects. One project's workspace was found and the other was not, even though both had a workspace file in root of the project. I'm not sure the difference or why one worked and the other didn't, but, either way, maybe we should take this conversation to auto-open-workspace at this point, since it's probably slightly off topic now. Shall I open an issue on your repo? |
@Natetronn yes, please do so :) |
Originally posted by @wottpal in #334 (comment)
The text was updated successfully, but these errors were encountered: