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.

Sign up for GitHub

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

Jump to bottom

Have a launch.json that uses the downloaded vscode, not the currently running one #211

Open
JustinGrote opened this issue Apr 7, 2023 · 0 comments
Open

Have a launch.json that uses the downloaded vscode, not the currently running one #211

JustinGrote opened this issue Apr 7, 2023 · 0 comments
Labels
feature-request Request for new features or functionality

Comments

@JustinGrote
Copy link

The launch configuration for "Run Extension Tests" references ${exeFile}, which is my current vscode, not the one that was downloaded. This should be enhanced to:

  1. Reference the downloaded one. This could be done with a env variable, a command variable, or a custom debugResolver with a new task type.
  2. Include the additional params from getProfileArguments, using the same method

Today I just hardcode these paths into my launch.json but it doesn't work cross-platform.
@connor4312 connor4312 added the feature-request Request for new features or functionality label Apr 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature-request Request for new features or functionality
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@connor4312 @JustinGrote