-
Notifications
You must be signed in to change notification settings - Fork 292
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
Firebase admin fix #111
Firebase admin fix #111
Conversation
Codecov Report
@@ Coverage Diff @@
## master #111 +/- ##
==========================================
- Coverage 75.89% 75.38% -0.51%
==========================================
Files 9 9
Lines 448 451 +3
==========================================
Hits 340 340
- Misses 108 111 +3
Continue to review full report at Codecov.
|
// remove me when node.js makes this the default behavior | ||
process.on("unhandledRejection", e => { | ||
throw e; | ||
}); |
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.
Where is this coming from? We should always try to handle the promises we create. Agreed that it's a good thing to add as a safeguard
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.
Good point - I've handled the rejection rather.
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 do like the safeguard. I strongly dislike Node's default mechanism
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.
Sure added it back too!
4285ae3
to
0262f52
Compare
Fixes #109, as well as improving the CLI error messages.