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
Adding Run and Debug buttons #48
Comments
came here to ask this as well. [
{
"key": "cmd+shift+0",
"command": "workbench.action.tasks.runTask",
"args": "Run Server"
}
]
The reason the default behavior does not work for me is I would like to be able to run multiple scripts in a split integrated terminal using a single command tasks.json {
"version": "2.0.0",
"tasks": [
{
"label": "Run Server",
"dependsOn": [
"PositionHandler",
"Strategy Runner",
"Mock Exchange",
]
},
{
"type": "npm",
"script": "runner",
"path": "Communications/",
"label": "Strategy Runner",
"presentation": {
"reveal": "always",
"clear": false,
"focus": true,
"group": "runner"
}
},
{
"type": "npm",
"script": "mockExchange",
"path": "Communications/",
"label": "Mock Exchange",
"presentation": {
"reveal": "always",
"clear": false,
"focus": true,
"group": "runner"
}
},
{
"type": "npm",
"script": "positionHandler",
"path": "Communications/",
"label": "PositionHandler",
"presentation": {
"reveal": "always",
"focus": true,
"clear": false,
"group": "runner"
}
}
]
} |
+1 A much needed feature |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, on VSCode the run and debug buttons are combined. This is inconvenient as if there are breakpoints present the program will enter debug mode. I have to rely on key binding which have separate commands for run (will ignore breakpoints) and debug. I tried to add these 2 commands in VSCode Action Buttons but I would get errors. Is there a way of making this work?
This is the error that I get:
I would assume is that it can only run commands from terminal and not VSCode. If this is the case, how can I make it run commands from VSCode?
The text was updated successfully, but these errors were encountered: