Skip to content
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

#cnsqa-1672 add new AfterResponseSend event #599

Open
wants to merge 11 commits into
base: master
Choose a base branch
from
Open

Conversation

lukasPan
Copy link
Contributor

No description provided.

Copy link

changeset-bot bot commented Jan 20, 2025

🦋 Changeset detected

Latest commit: e8f0dc5

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
Name Type
@ima/hmr-client Patch
@ima/server Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@@ -205,6 +206,7 @@ module.exports = function serverAppFactory({

res.status(context.response.status);
res.send(context.response.content);
await emitter.emitParallel(Event.AfterResponseSend, event);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need a try catch block here and we can use logger.error to print some info (see

logger.error('The application crashed due to an uncaught exception', {
for inspiration)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, about the discussions earlier today, this code should not be reached twice in any scenario, because of the res.headersSent check above, so we do not need to do any additional handling here.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

try-catch block with logger.error added

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you used a little bit different log structure compared to the one i linked above (logger.error('...', { error }) vs. logger.error('...', error)), it would be nice to keep it consistent

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Log structure fixed to be consistent with others

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants