-
Notifications
You must be signed in to change notification settings - Fork 29.5k
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
Test: Ability to select and start a launch using keyboard #20982
Comments
@michelkaporin fyi - please set milestone and testplan-item label |
@jrieken I don't have permissions for this yet, unfortunately. Thanks for the notice anyway! |
doh. didn't know that... hope that changes soon |
I keep getting confused between "task" and "launch" configurations, that is I try to use the command pallet to start a debug "task" and wonder why there's nothing there. In my mental model I see both as doing the same thing: running something. One is interactive (i.e. debug) while the other isn't. Might this be an opportunity to merge/unify these somehow under a single keyword/alias? e,g.
|
@MartinSGill Thank you for your comment. Task and debug concepts are different. The first one is used to automate tasks like building, packaging, testing or deploying, whereas the other one configures the way you want to debug your program. Merging those two concepts into one would be wrong from simple software design perspective, and would lead to those concepts collision, as essentially they target two different purposes. Therefore, reference to them is kept under different keywords/aliases. Please see the links below for further reference. |
Verified on Linux |
Verified on Mac |
Complexity: 1
Refs: #16613
We have introduced an ability to select and launch debug configuration through the command palette.
Verify:
debug
with space at the end. The list of all debug configurations listed in launch.json should appear.>Debug: Select and Start Debugging
, option should appear, upon clicking should be presented with a list of all launch configs.The text was updated successfully, but these errors were encountered: