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.

Sign up for GitHub

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

Jump to bottom

VSCode is no longer supporting "startSessionCommand" contribution #24

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

VSCode is no longer supporting "startSessionCommand" contribution #24

isidorn opened this issue Nov 6, 2017 · 1 comment
Assignees
@kimushu
Labels
vscode

Comments

@isidorn
Copy link

isidorn commented Nov 6, 2017

Hi,

We noticed your extension in package.json is using a "startSessionCommand" 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 "startSessionCommand" 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
@kimushu kimushu mentioned this issue Nov 7, 2017
Closed
@kimushu kimushu self-assigned this Nov 7, 2017
@kimushu kimushu added the vscode label Nov 7, 2017
@kimushu kimushu modified the milestone: 1.0.0 Nov 7, 2017
kimushu referenced this issue Nov 9, 2017
@kimushu
Remove startSessionCommand
05bd110
@kimushu
Copy link
Owner

kimushu commented Nov 10, 2017

Fixed. (v0.99.12)

@kimushu kimushu 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
Assignees

@kimushu kimushu

Labels
vscode
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kimushu @isidorn