-
Notifications
You must be signed in to change notification settings - Fork 386
Closed
Milestone
Description
Hey,
VSCode dev here. This milestone I am looking into simplifing generated launch.json
for various extensions microsoft/vscode#62851
The launch.json
that Java generates is attached at the end. This is not too complex for the avarage user, however we can still improve. I suggest to simplify it the following way:
-
DebugConfigurationProvider
should use thequickPick
to ask the user if he would like to launch or to attach. After that it should ask what is themainClass
or what is theport
. Optimally it should be able to detect those things on its own, but if not possible usequickPick
to ask the user. - Remove default fields which are not necessery like
console
,args
,stopOnEntry
,hostName
andcwd
- You are already contributing
configuraitonSnippets
which is great. However these snippets also need to be simplified. I suggest to remove all attributes that have the default value. Example:stopAtEntry
,cwd
,args
If you agree with the suggestions I am making here I am also here to help with any potential questions you might have. The changes should not require a lot of work but will simplify the flow a lot imho. It should be much less complex and not too much like a wizard experience
{
// 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": [
{
"type": "java",
"name": "Debug (Launch)",
"request": "launch",
"cwd": "${workspaceFolder}",
"console": "internalConsole",
"stopOnEntry": false,
"mainClass": "",
"args": ""
},
{
"type": "java",
"name": "Debug (Attach)",
"request": "attach",
"hostName": "localhost",
"port": "<debug port of remote debuggee>"
}
]
}
Metadata
Metadata
Assignees
Labels
No labels