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
Log shell.openExternal
errors
#8246
Conversation
Electron's shell.openExternal changed to become async so in order to ensure that errors don't get lost in the async void we need to explicitly catch them. I'm choosing to log them rather than throw because surfacing the error to the user doesn't add any value. They'll notice that something is wrong by virtue of the fact that their browser didn't open correctly. The logging will be helpful for us developers when we're trying to debug what went wrong.
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.
Just a quick note about the invocation of our logging methods. Out of curiosity, can you give an example of where this method would throw? I don't believe I've ever seen that before.
took a quick pass at this to get it across the line after discussing briefly with @kuychaco on friday. i had misunderstood
|
Overview
This is a follow-on PR to #8220, which had closed #8156
Description
Electron's
shell.openExternal
changed to become async so in order to ensure that errors don't get lost in the async void we need to explicitly catch them.I'm choosing to log them rather than throw because surfacing the error to the user doesn't add any value. They'll notice that something is wrong by virtue of the fact that their browser didn't open correctly.
The logging will be helpful for us developers when we're debugging what went wrong and save us time identifying the root cause.
Release notes
Notes: no-notes