| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
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.
I was just looking at this too. Couple of suggestions.
Sorry, something went wrong.
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? |
Sorry, something went wrong.
|
Thanks for the reminder. I don't think this is a required fix for GHES 3.4. I will hold off on the merge. |
Sorry, something went wrong.
There was a problem hiding this comment.
A couple of suggestions, otherwise LGTM to get in after the GHES 3.4 release.
Sorry, something went wrong.
|
I've done the release that is going into GHES 3.4 so please do not consider this blocked on that anymore 👍🏼 |
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks!
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
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.
Merge / deployment checklist