Add option to run everything in the current file

[tgodzik]

This will enable the possibility to run/debug without specifying the configuration in launch.json

Some further work can be done on the discovery so that we would be able to automatically feel new configurations for the user.

Related to #3272

[ayoub-benali]

Does this still requires DAP support from the client ?
In the case of sublime DAP would handled by a separate plugin https://github.com/daveleroy/sublime_debugger (similarly to vim ?). That plugin also seems to require a config file which is confusing in term of setup

[tgodzik]

Does this still requires DAP support from the client ? In the case of sublime DAP would handled by a separate plugin https://github.com/daveleroy/sublime_debugger (similarly to vim ?). That plugin also seems to require a config file which is confusing in term of setup

It does require some kind of DAP client, but the command should start the process and return the port to connect to. So some work on the editor side is required to wire the output of the command and starting of the session.

[ayoub-benali]

Thanks for the clarification. Is this simplification only for running files ? do test cases for example require the "old" way (config file).

[tgodzik]

Thanks for the clarification. Is this simplification only for running files ? do test cases for example require the "old" way (config file).

Actually the aim of the PR is to provide an universal way of running things:

• if there is a main class in the file, run that
• if there are multiple main classes, show quickpick and run the chosen class
• if there are test classes, run all of them

[ckipp01]

Couple nits, but other than that LGTM! I tried it out with nvim-metals and all seemed to work well!

[ckipp01]

Total aside, but on my TODO list to to refactor all this fails out. I'm not a huge fan of using failing futures for control flow. I think we can probably model all of these differently. One day 😆

[kpodsiad]

Are you talking about a dedicated error channel?