381c5cb15c
Modified the previous implementation of the whiteboard individual access to remove multiple Collections dependency on this feature. Multi-user whiteboard is now an array instead of a boolean value and most of the access control can be synchronized and handled by akka-apps.
33 lines
1014 B
JavaScript
33 lines
1014 B
JavaScript
import RedisPubSub from '/imports/startup/server/redis';
|
|
import { Meteor } from 'meteor/meteor';
|
|
import { check } from 'meteor/check';
|
|
import { getMultiUser } from '/imports/api/whiteboard-multi-user/server/helpers';
|
|
import { extractCredentials } from '/imports/api/common/server/helpers';
|
|
|
|
export default function addIndividualAccess(whiteboardId, userId) {
|
|
const REDIS_CONFIG = Meteor.settings.private.redis;
|
|
const CHANNEL = REDIS_CONFIG.channels.toAkkaApps;
|
|
const EVENT_NAME = 'ModifyWhiteboardAccessPubMsg';
|
|
|
|
check(whiteboardId, String);
|
|
check(userId, String);
|
|
|
|
const { meetingId, requesterUserId } = extractCredentials(this.userId);
|
|
|
|
check(meetingId, String);
|
|
check(requesterUserId, String);
|
|
|
|
const multiUser = getMultiUser(meetingId, whiteboardId);
|
|
|
|
if (!multiUser.includes(userId)) {
|
|
multiUser.push(userId);
|
|
|
|
const payload = {
|
|
multiUser,
|
|
whiteboardId,
|
|
};
|
|
|
|
return RedisPubSub.publishUserMessage(CHANNEL, EVENT_NAME, meetingId, requesterUserId, payload);
|
|
}
|
|
}
|