Skip to content
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

Support numeric input variables #66697

Closed
amcasey opened this issue Jan 18, 2019 · 2 comments
Closed

Support numeric input variables #66697

amcasey opened this issue Jan 18, 2019 · 2 comments
Assignees
Labels
*caused-by-extension Issue identified to be caused by an extension debug Debug viewlet, configurations, breakpoints, adapter issues feature-request Request for new features or functionality
Milestone

Comments

@amcasey
Copy link
Member

amcasey commented Jan 18, 2019

I'd like to be able to use input variables to select the port to attach to in my (NodeJS debugging) launch configuration.

        "inputs": [
            {
                "id": "debugPort",
                "description": "Which port do you want to attach to?",
                "default": 9229,
                "type": "pickString",
                "options": [ 9229, 9230, 9239, 9329, 5870 ]
            }
        ]

It seems quite likely that substituting a numeric value will be difficult/impossible, so it might be necessary to accept strings for "port" property of launch configurations.

In a perfect world, I'd also be able to alias the ports in the combo box: "default" for 9229, "VS Code Extension" for 5870, etc.

@weinand weinand added debug Debug viewlet, configurations, breakpoints, adapter issues feature-request Request for new features or functionality labels Jan 18, 2019
@weinand weinand added this to the Backlog milestone Feb 6, 2019
@weinand
Copy link
Contributor

weinand commented Nov 5, 2020

Yes, variable substitution in VS Code only works within strings.
If you want to use it for non-string typed launch config properties, you will have to ask the extension author to support strings as an alternative type.

@weinand weinand added the *caused-by-extension Issue identified to be caused by an extension label Nov 5, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Dec 22, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*caused-by-extension Issue identified to be caused by an extension debug Debug viewlet, configurations, breakpoints, adapter issues feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

3 participants
@weinand @amcasey and others