The launch.json created from the "Run and Debug" pane does not contain all fields required by the extension.
It shows a validation warning about the generated launch config
What I expected to happen
That the launch.json would contain all required fields and be ready to launch. It is confusing to see the validation warning, even though it works if you ignore the warning and run.
Suggestions
Instead of using the unset data property to prompt for the file we allow the property to be either a file path or a flag like prompt-for-file? Or perhaps more idiomatic would be to add another VS Code command that can be set by default that works like ${workspaceFolder}/${command:AskForProgramName}.
This would provide a more explicit default profile and also would would help custom profiles created by users to be more understandable.
Steps to reproduce
What happened
The launch.json created from the "Run and Debug" pane does not contain all fields required by the extension.
It shows a validation warning about the generated launch config
What I expected to happen
That the launch.json would contain all required fields and be ready to launch. It is confusing to see the validation warning, even though it works if you ignore the warning and run.
Suggestions
Instead of using the unset
dataproperty to prompt for the file we allow the property to be either a file path or a flag likeprompt-for-file? Or perhaps more idiomatic would be to add another VS Code command that can be set by default that works like${workspaceFolder}/${command:AskForProgramName}.This would provide a more explicit default profile and also would would help custom profiles created by users to be more understandable.