Navigation Menu

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 #2

Closed
isidorn opened this issue Nov 6, 2017 · 1 comment
Assignees

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

@vknabel vknabel self-assigned this Nov 7, 2017
vknabel added a commit that referenced this issue Nov 10, 2017
@vknabel
Copy link
Owner

vknabel commented Nov 10, 2017

@isidorn Thank you very much for your report! The latest release is now compatible.

@vknabel vknabel closed this as completed Nov 10, 2017
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

No branches or pull requests

2 participants