-
Notifications
You must be signed in to change notification settings - Fork 26
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
VSCode is no longer supporting specifiying a commandId in the "initialConfigurations" contribution #39
Comments
I got hit by this issue today. The extension refused to provide configurations and I have to copy them manually from source to the launch.json file like below:
|
Same, I get only this when I use the command to generate configuration: { |
to use vscode.DebugConfigurarationProvider (rogalmic#39). Follow changes in https://github.com/Microsoft/vscode-mock-debug/blob/master/package.json till 0915e40 (Wed Nov 22 15:46:43 2017 +0100) since ours is based on it (maybe at arround e6022ad, Fri Sep 23 18:39:48 2016 +0200).
to use vscode.DebugConfigurarationProvider (rogalmic#39). Follow changes in https://github.com/Microsoft/vscode-mock-debug/blob/master/package.json till 0915e40 (Wed Nov 22 15:46:43 2017 +0100) since ours is based on it (maybe at arround e6022ad, Fri Sep 23 18:39:48 2016 +0200).
to use vscode.DebugConfigurarationProvider (rogalmic#39). Follow changes in https://github.com/Microsoft/vscode-mock-debug/blob/master/package.json till 0915e40 (Wed Nov 22 15:46:43 2017 +0100) since ours is based on it (maybe at arround e6022ad, Fri Sep 23 18:39:48 2016 +0200).
Hi,
We noticed your extension in
package.json
is using a"initialConfigurations"
contribution in a deprecated way by specifiying a command id.We wanted to let you know that we plan to delete support for this specific use of "initialConfigurations" soon.
More about this deprecation can be found here and in our release notes.
A good example on how to use the
DebugConfigurarationProvider
which is the new way of doing this can be found hereAlso note other deprecations which are specified in our release notes (which can be found on our site).
Kind regards,
Isidor from the VSCode team
The text was updated successfully, but these errors were encountered: