Add debug configurationSnippets to package.json to light up "Add Configuration" experience

[rkeithhill]

See microsoft/vscode#16937 for details.

[rkeithhill]

What do you think about this impl of the debug configurationSnippets:

This is what the Start Debugging target drop down looks like. Note that I want to rename the current target PowerShell to PowerShell Launch (current file). This will allow the user to use the Add Configuration button in VSCode 1.8 to add new configurations that launch specific scripts. The user can then switch between the various targets in the Debug view drop down.

By renaming to PowerShell Launch ... this makes room for an eventual PowerShell Attach. :-)

Thoughts? I'd like to get this in for 0.8.0. I need to test this in VSCode 1.7 but @isidorn says 1.7 should just ignore the new configurationSnippets section.

[rkeithhill]

Been playing with this. I like it! It is not uncommon to have different scripts with a workspace that you want launched for debugging. This feature allows you to do that:

[daviwil]

I like the config naming a lot, makes things really clear. I think we'll get attach to process going pretty soon so it's good to leave room for that, as you have. Also good to be consistent with other extensions.

Hmmm, seems they're running a little late on 1.8, but maybe they'll ship soon after we do and it won't matter. I guess the biggest issue is whether there will be a way to create a default PowerShell launch config in that window of time. If it won't be possible then maybe we should either delay the release or hold off on the change until January. What do you think?

[rkeithhill]

I tried the extension in VSCode 1.7 and was able to create a launch.json file from the Debug view. The only differences are that the configuration name is the updated name and instead of "program" it uses "script". That should work just fine for a person using the launch.json file on the same machine they upgraded to 0.8.0. However if that get's checked in and someone else clones it and tries to debug from a machine with <= 0.7.2 they will get an error. Easy solution though - they upgrade to 0.8.0.

[isidorn]

@rkeithhill looks great!

[rkeithhill]

@isidorn Thanks for the feedback!