Skip to content

Add startSessionCommand handler for debugger configuration #431

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

Merged
merged 1 commit into from
Jan 13, 2017

Conversation

daviwil
Copy link
Contributor

@daviwil daviwil commented Jan 13, 2017

This change leverages the new "setSessionCommand" configuration parameter
for debugger contributions which allows us to provide a command that will
take a debug launch configuration, tweak it, and then launch the debugger
ourselves. This allows us to do any necessary launching or
pre-configuration of our debug adapter. It also allows us to create a
default launch configuration on the fly if one doesn't already exist.
This means that users can now debug the current script without a
launch.json either with or without a folder open!

@daviwil daviwil added this to the 0.9.0 milestone Jan 13, 2017
@daviwil
Copy link
Contributor Author

daviwil commented Jan 13, 2017

I'm really happy with how well this works. And the best part is that it's compatible with VS Code 1.8.1 because it's only additive, no changes to existing debugger configurations, etc. I'll ship it with 0.9.0 and it'll light up as soon as VSC 1.9.0 ships.

@daviwil daviwil changed the title Add setSessionCommand handler for debugger configuration Add startSessionCommand handler for debugger configuration Jan 13, 2017
This change leverages the new "startSessionCommand" configuration parameter
for debugger contributions which allows us to provide a command that will
take a debug launch configuration, tweak it, and then launch the debugger
ourselves.  This allows us to do any necessary launching or
pre-configuration of our debug adapter.  It also allows us to create a
default launch configuration on the fly if one doesn't already exist.
This means that users can now debug the current script without a
launch.json either with or without a folder open!
@daviwil daviwil force-pushed the daviwil/debug-launch branch from 989edc1 to aa99387 Compare January 13, 2017 15:44
@daviwil daviwil merged commit b8b8b0b into master Jan 13, 2017
@daviwil daviwil deleted the daviwil/debug-launch branch January 13, 2017 18:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants