-
Notifications
You must be signed in to change notification settings - Fork 329
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
Ensure loadApiError is caught #882
Conversation
And add a better error message. By using `void` instead of `await`, any error thrown is not caught by surrounding try-catch blocks. I could continue to use `void` and explicitly handle any thrown errors by using `.catch`, but most likely the time savings is minimal and this makes the code more complex.
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.
I was just looking at this too. Couple of suggestions.
Discussion here #882 (comment) shows that properly handling preloading feature flag errors is complex and the benefit we get from it does not offset the complexity.
I haven't reviewed the code since Henry seems to have it covered (although happy to if you would like another set of eyes), but could I ask to hold off merging this until Tuesday since it seems like a potentially risky change to put into GHES 3.4 at the last minute? |
Thanks for the reminder. I don't think this is a required fix for GHES 3.4. I will hold off on the merge. |
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.
A couple of suggestions, otherwise LGTM to get in after the GHES 3.4 release.
I've done the release that is going into GHES 3.4 so please do not consider this blocked on that anymore 👍🏼 |
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.
Thanks!
20dbc92
to
806fc12
Compare
And add a better error message.
By using
void
instead ofawait
, any error thrown is not caughtby surrounding try-catch blocks.
I could continue to use
void
and explicitly handle any thrown errorsby using
.catch
, but most likely the time savings is minimal andthis makes the code more complex.
Merge / deployment checklist