You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 17, 2019. It is now read-only.
Since the latest stable release included support for multi root workspaces, I guess it is important for this extension to follow the guidelines for adapting to the new API.
In particular, I have found references to the now deprecated workspace.rootPath: master branch
Also, for the commands like creating a package/running a build, we should probably ask the user which workspace folder they want to add the package to/run the build in.
Any other ideas, in accordance to the changes as listed in the linked wiki?
I will read further into it.
The text was updated successfully, but these errors were encountered:
I don't think it would be common have more than one ROS workspace open at a time. I think a good solution is to scan all vscode workspace folders for all ROS workspaces, and if there's more than one unique one either:
Show an error.
Show a picker for the user to choose one.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Since the latest stable release included support for multi root workspaces, I guess it is important for this extension to follow the guidelines for adapting to the new API.
In particular, I have found references to the now deprecated
workspace.rootPath
:master branch
4-catkin-tools-support branch
Also, for the commands like creating a package/running a build, we should probably ask the user which workspace folder they want to add the package to/run the build in.
Any other ideas, in accordance to the changes as listed in the linked wiki?
I will read further into it.
The text was updated successfully, but these errors were encountered: