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
fix: report more detailed errors in shell.openExternal() on Windows #33620
Conversation
1cbbb6c
to
dfbff9d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Release Notes Persisted
|
I have automatically backported this PR to "15-x-y", please check out #33656 |
I have automatically backported this PR to "16-x-y", please check out #33657 |
I have automatically backported this PR to "17-x-y", please check out #33658 |
I have automatically backported this PR to "18-x-y", please check out #33659 |
I have automatically backported this PR to "19-x-y", please check out #33660 |
/trop run backport-to 18-x-y |
The backport process for this PR has been manually initiated - sending your PR to |
I have automatically backported this PR to "18-x-y", please check out #33705 |
Description of Change
Report more detailed errors in
shell.openExternal()
on Windows.Before:
After:
Checklist
npm test
passesRelease Notes
Notes:
shell.openExternal()
now reports more detailed errors on Windows.