Skip to content

debug: add argsString as launch property so we can use vscode inputs to setup the debuggee parameter in a promptString #1223

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
LucaHermann opened this issue Feb 11, 2021 · 2 comments
Labels
Debug Issues related to the debugging functionality of the extension. FeatureRequest NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.

Comments

@LucaHermann
Copy link

The problem is that currently the vscode-go extension only accepts args as an array or string and there is no easy way to take a string as an input from user and convert it to a splitted string array.

Therefore I propose that we add a property "argsString" that is a simple string which overrides "args" property if set (or vice-versa).

Here is my current code, feel free to propose any alternative solution.

Launch.json

configurations: [
    {
      "name": "GO -> Debug",
      "type": "go",
      "request": "launch",
      "mode": "debug",
      "program": "${workspaceFolder}/go/cmd/zenlaw",
      "cwd": "${workspaceFolder}/go",
      "argsString": ${input:processArgs}
    },
],
"inputs": [
    {
      "id": "processArgs",
      "description": "enter subcommands and flags",
      "type": "promptString",
    },
  ]
@hyangah hyangah changed the title add argsString as launch property so we can use vscode inputs to setup the debuggee parameter in a promptString debug: add argsString as launch property so we can use vscode inputs to setup the debuggee parameter in a promptString Feb 11, 2021
@Z-a-r-a-k-i
Copy link

See: microsoft/vscode-python-debugger#63

Would be so nice

@hyangah hyangah added the HelpWanted Issues that are not prioritized by the maintainers. Help is requested from community contributors. label Feb 16, 2021
@hyangah hyangah added NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. and removed HelpWanted Issues that are not prioritized by the maintainers. Help is requested from community contributors. labels Feb 17, 2021
@polinasok polinasok added the Debug Issues related to the debugging functionality of the extension. label Feb 19, 2021
@suzmue
Copy link
Contributor

suzmue commented Feb 23, 2021

It seems like the vscode team is considering adding their own implementation (microsoft/vscode#83678) of this feature. If they do, then our users would benefit directly without a change to our extension.

Please be sure to add your support to that issue if you would like this feature!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Debug Issues related to the debugging functionality of the extension. FeatureRequest NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Development

No branches or pull requests

6 participants