[debug] automatically create 'launch.json'

[vince-fugnitto]

What it does

Currently, when attempting to execute the command Start Debugging without a launch.json present under .theia or .vscode nothing occurs. The change ensures that if no configurations are found, the launch.json is automatically created and users are then prompted to select their debug configuration type template.

Additional steps will need to be done in the future to prompt the quick-open described in #6489.

How to test

1. start the application with a workspace that currently does not have a .launch.json
2. attempt to execute the command Start Debugging
3. the command will automatically create the launch.json if not present, and will prompt users in the editor to select the type of config
4. the same scenario should work with a launch.json except the debugging should begin

Review checklist

• as an author, I have thoroughly tested my changes and carefully followed the review guidelines

Reminder for reviewers

• as a reviewer, I agree to behave in accordance with the review guidelines

Signed-off-by: Vincent Fugnitto vincent.fugnitto@ericsson.com

[lmcbout]

May be on another PR, but If the end-user close the "Debug console" voluntary or not and he starts the debug session again, he does not see the end result. May be if the "Debug console" is closed when initiating the debug, we should open the "Debug console" view?

Otherwise, looks good to me

[lmcbout]

"If not current ..." or "If no current..."

[vince-fugnitto]

May be on another PR, but If the end-user close the "Debug console" voluntary or not and he starts the debug session again, he does not see the end result. May be if the "Debug console" is closed when initiating the debug, we should open the "Debug console" view?

@lmcbout I'm not sure I understand what you mean, could you clarify?

[lmcbout]

If "Debug console" view is closed when you try to run the Debug session, the "Debug console" view will not show up and we don't see the result of the execution. May be if we don't see the execution result, we should open the "Debug console" view if closed to see the result.

[vince-fugnitto]

If "Debug console" view is closed when you try to run the Debug session, the "Debug console" view will not show up and we don't see the result of the execution. May be if we don't see the execution result, we should open the "Debug console" view if closed to see the result.

@lmcbout are you referring to when no launch.json exists and a user attempts to start debugging? I see the following behavior:

1. launch.json exists - the debug console is displayed and the debugging starts
2. no launch.json exists - the file is created, and users are prompted to add a new config

I don't see why the debug console would be opened for the second case, the same behavior is also present in VS Code.

[elaihau]

looks good to me. Thank you !

[akosyakov]

Why do we need to create an empty file? I don't think VS Code does it. Does it really fix #6489?

[vince-fugnitto]

Why do we need to create an empty file? I don't think VS Code does it. Does it really fix #6489?

It doesn't just create an empty file, it creates the file with the default launch schema, and also prompts users to add specific configs (for instance, creating a mocha test config):

---

It is the same functionality present when executing the play button from the debug-view from master.

[akosyakov]

It is the same functionality present when executing the play button from the debug-view from master.

Can we reuse it?

[vince-fugnitto]

It is the same functionality present when executing the play button from the debug-view from master.

Can we reuse it?

I refactored further so we can re-use the same logic present in the actual command.
Thanks for the idea!

[akosyakov]

code wise looks good now, thank you

[vince-fugnitto]

code wise looks good now, thank you

Thank you for your help in making it better 👍