Accept additional parameter argsString for arguments in string format

[felipecrs]

VS Code does not support passing arguments to args in a string instead of an array of string. See microsoft/vscode#83678.

However, due to that, is impossible for users to use "prompt for arguments" when launching a debug session.

VS Code team suggest the extension owners to provide an additional parameter for debbuging configuration. See microsoft/vscode#83678 (comment)

It would look like then:

{
  "version": "0.2.0",
  "configurations": [
      {
        "type": "bashdb",
        "request": "launch",
        "name": "Bash-Debug (simplest configuration)",
        "program": "${file}",
        "cwd": "${workspaceFolder}",
        "argsString": "-foo -bar /hello/world -o -p"
      }
    ]
}

And then, we would be able to do something like:

{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "bashdb",
      "request": "launch",
      "name": "Bash-Debug (simplest configuration)",
      "program": "${file}",
      "cwd": "${workspaceFolder}",
      "argsString": "${input:arguments}"
    }
  ],
  "inputs": [
    {
      "id": "arguments",
      "type": "promptString",
      "default": "--help",
      "description": "The arguments to pass to the script"
    }
  ]
}

[rogalmic]

This will break the integrated/external terminal, since the vscode api used for those requires array of args. See RunInTerminalRequest + RunInTerminalRequestArguments.

Having said that, I would also prefer to pass full args as one string, but it will be possible only when mentioned api methods allow to specify to use bash explicitly + provide command as single string.

[felipecrs]

So how about transforming the commandline string into an array?

[rogalmic]

Well, this requires handling of arg quoting, which proves to be hard and should not be part of extension. Args are sometimes more complex values.

[felipecrs]

@rogalmic do you mind taking a look at microsoft/vscode#97655 and cast your vote if you agree?