Skip to content

Commit 9498198

Browse files
committed
fix: error when message doesn't have initiatorUserId
So far I guess we don't have such a case as there were no issues raised. But if some messages don't have initiatorUserId, there would be an error during requesting user details.
1 parent 95c4cd9 commit 9498198

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

connect/connectNotificationServer.js

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -451,9 +451,13 @@ const handler = (topic, message, logger, callback) => {
451451
logger.debug('filtered notifications: ', allNotifications);
452452
// now let's retrieve some additional data
453453

454+
const ids = [];
455+
logger.debug(message.initiatorUserId, 'message.initiatorUserId');
456+
if (message.initiatorUserId) {
457+
ids.push(message.initiatorUserId);
458+
}
454459
// if message has userId such messages will likely need userHandle and user full name
455460
// so let's get it
456-
const ids = [message.initiatorUserId];
457461
logger.debug(message.userId, 'message.userId');
458462
if (message.userId) {
459463
ids.push(message.userId);

0 commit comments

Comments
 (0)