-
Notifications
You must be signed in to change notification settings - Fork 56
fix(PM-1175): Applied email not sent #820
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
Conversation
if (!isCreatorPartofSubjects) { | ||
listOfSubjects.push({ | ||
email: creator[0].email, | ||
handle: creator[0].handle, | ||
}); | ||
} | ||
} | ||
|
||
req.log.debug(listOfSubjects, 'final list of subjects'); |
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.
Consider removing or adjusting the debug log statement if it is not needed for production. Debug logs can be useful during development but may clutter the log files in a production environment.
|
||
const creator = await util.getMemberDetailsByUserIds([opportunity.createdBy], req.log, req.id); | ||
|
||
req.log.debug(creator, 'creator', opportunity.createdBy); |
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.
The addition of opportunity.createdBy
to the debug log statement provides more context, which can be useful for debugging purposes. However, ensure that this additional information does not expose sensitive data. If opportunity.createdBy
contains sensitive information, consider masking or obfuscating it before logging.
What's in this PR?