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

Closed
isidorn opened this issue Nov 6, 2017 · 2 comments · Fixed by #44

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

@tusharjoshi
Copy link

tusharjoshi commented Nov 28, 2017

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:

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
		{
			"name": "Bash-Debug (hardcoded script name)",
			"type": "bashdb",
			"request": "launch",
			"scriptPath": "${workspaceRoot}/agent_memo.sh",
			"commandLineArguments": "",
			"windows": {
				"bashPath": "C:\\Windows\\sysnative\\bash.exe"
			},
			"linux": {
				"bashPath": "bash"
			},
			"osx": {
				"bashPath": "bash"
			}
		},
		{
			"name": "Bash-Debug (select script from list of sh files)",
			"type": "bashdb",
			"request": "launch",
			"scriptPath": "${command:SelectScriptName}",
			"commandLineArguments": "",
			"windows": {
				"bashPath": "C:\\Windows\\sysnative\\bash.exe"
			},
			"linux": {
				"bashPath": "bash"
			},
			"osx": {
				"bashPath": "bash"
			}
        },
		{
			"name": "Bash-Debug (type in script name)",
			"type": "bashdb",
			"request": "launch",
			"scriptPath": "${workspaceRoot}/${command:AskForScriptName}",
			"commandLineArguments": "",
			"windows": {
				"bashPath": "C:\\Windows\\sysnative\\bash.exe"
			},
			"linux": {
				"bashPath": "bash"
			},
			"osx": {
				"bashPath": "bash"
			}
        }
	]
}

@AntonKrug
Copy link

Same, I get only this when I use the command to generate configuration:

{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": "extension.bash-debug.provideInitialConfigurations"
}

wataash added a commit to wataash/vscode-bash-debug that referenced this issue Dec 11, 2017
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).
wataash added a commit to wataash/vscode-bash-debug that referenced this issue Dec 17, 2017
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).
wataash added a commit to wataash/vscode-bash-debug that referenced this issue Dec 17, 2017
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).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants