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

don't require workspace folder arg for --profile-temp option when debugging extensions #159577

Closed
weinand opened this issue Aug 30, 2022 · 2 comments
Closed

don't require workspace folder arg for --profile-temp option when debugging extensions #159577

weinand opened this issue Aug 30, 2022 · 2 comments
Assignees
@sandy081
Labels
bug Issue identified by VS Code Team member as probable bug insiders-released Patch has been released in VS Code Insiders user-profiles User profile management verified Verification succeeded
Milestone
September 2022

Comments

@weinand
Copy link
Contributor

weinand commented Aug 30, 2022 •
edited
Loading

When debugging an extension the --profile-temp should just work for the VS Code window that opens (and has the extension under development).
Requiring an additional workspace folder argument is unexpected and difficult to explain to users.

For additional context see: #159572 (comment) and #154460 (comment)
@weinand weinand mentioned this issue Aug 30, 2022
Closed
@sandy081 sandy081 added bug Issue identified by VS Code Team member as probable bug user-profiles User profile management labels Aug 31, 2022
@sandy081 sandy081 added this to the September 2022 milestone Aug 31, 2022
sandy081 added a commit that referenced this issue Sep 6, 2022
@sandy081
fix #159577
a75c785
@vscodenpa vscodenpa added the unreleased Patch has not yet been released in VS Code Insiders label Sep 6, 2022
@weinand
Copy link
Contributor Author

weinand commented Sep 6, 2022

@sandy081 great, I'll give it a try...

@vscodenpa vscodenpa added insiders-released Patch has been released in VS Code Insiders and removed unreleased Patch has not yet been released in VS Code Insiders labels Sep 7, 2022
@weinand
Copy link
Contributor Author

weinand commented Sep 8, 2022

This works fine now.

@weinand weinand added the verified Verification succeeded label Sep 8, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Oct 21, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@sandy081 sandy081

Labels
bug Issue identified by VS Code Team member as probable bug insiders-released Patch has been released in VS Code Insiders user-profiles User profile management verified Verification succeeded
Projects
None yet
Milestone
September 2022
Development

No branches or pull requests
3 participants
@weinand @sandy081 @vscodenpa