Skip to content
This repository has been archived by the owner on Jan 13, 2021. It is now read-only.

VSCode is no longer supporting specifiying a commandId in the "initialConfigurations" contribution #32

Closed
isidorn opened this issue Nov 6, 2017 · 2 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

@raix
Copy link
Owner

raix commented Feb 12, 2018

Hi @isidorn thanks man - I'm going to look a bit into this, it seems to be a user issue that debug configurations often are platform specific - so a provider seems to be the way to go.

@hoehrmann
Copy link
Collaborator

@raix: This is fixed now.

@raix raix closed this as completed Mar 2, 2019
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

3 participants