Skip to content
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 #1207

Closed
isidorn opened this issue Nov 6, 2017 · 3 comments

Comments

@isidorn
Copy link

isidorn commented Nov 6, 2017

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 here

Also note other deprecations which are specified in our release notes (which can be found on our site).

Kind regards,
Isidor from the VSCode team

@bobbrow
Copy link
Member

bobbrow commented Nov 6, 2017

I believe @pieandcakes has already addressed this and it will be updated in our release this week. Thanks.

@bobbrow bobbrow closed this as completed Nov 6, 2017
@pieandcakes
Copy link
Contributor

@WardenGnaw this is something you fixed right?

@WardenGnaw
Copy link
Member

@pieandcakes Yes.

@github-actions github-actions bot locked and limited conversation to collaborators Oct 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants