The feature request is to support dynamic validation/intellisense during editing launch.json.
Below is the background:
When implementing a new debug type, currently we could define the type for each properties of launch.json in the package.json, and VS Code will auto apply the type validation to launch.json. This may work for most of cases. But in some scenarios, we hope validate the type not only, but also validate the value during editing launch.json.
For example, in Java Debugger, we have two important configs mainClass and projectName, the user will be very likely to configure an incorrect value if manually configure it. The type validation cannot find such errors in advance, so that the errors are reported at a much later stage. This does harm to the user experience.
Thanks to the configuration provider, we can do some code validation before launching debugger, but this kind of validation is still at running step, not at configuration step. And it's an UX challenge about how to friendly guide the user about the right configs through the runtime QuickPick.
The natural idea is to provide the intellisense directly when the user is editing the launch.json. Comparing other IDES, such as Intellij and Eclipse, they have special UI for the debug configurations and support Selection for the complex config at the configuration step.
The feature request is to support dynamic validation/intellisense during editing launch.json.
Below is the background:
When implementing a new debug type, currently we could define the type for each properties of launch.json in the package.json, and VS Code will auto apply the type validation to launch.json. This may work for most of cases. But in some scenarios, we hope validate the type not only, but also validate the value during editing launch.json.
For example, in Java Debugger, we have two important configs
mainClassandprojectName, the user will be very likely to configure an incorrect value if manually configure it. The type validation cannot find such errors in advance, so that the errors are reported at a much later stage. This does harm to the user experience.Thanks to the configuration provider, we can do some code validation before launching debugger, but this kind of validation is still at running step, not at configuration step. And it's an UX challenge about how to friendly guide the user about the right configs through the runtime QuickPick.
The natural idea is to provide the intellisense directly when the user is editing the launch.json. Comparing other IDES, such as Intellij and Eclipse, they have special UI for the debug configurations and support Selection for the complex config at the configuration step.
