-
Notifications
You must be signed in to change notification settings - Fork 43
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
CHES Notifications & Logger Adjustment #2730
Conversation
🚀 Deployment Information The Express API Image has been built with the tag: |
Code Climate has analyzed commit ae31ff2 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 93.4%. View more on Code Climate. |
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.
Failed email log printing as expected, and notifications set to failed in project page.
🎯 Summary
This is in response to the issue I had this morning with sending/resending notifications.
It turned out that my email in the database was not a real email from testing another ticket. This caused the CHES request to fail, but it wasn't very clear why it was doing so.
Changes
The logger now reports the stack if you log something that is of type Error.
logger.error(new Error('something went wrong'));
logger.error('this is not type error');
If the API is not in its containerized form, it will also pretty print the logs for easier readability
If the response is bad in some way or empty, sendAsync should now return null, which just marks attempted notifications as Failed.
Testing
blank
.🔰 Checklist