refactor: comment out collaborator ID update logic in CollaborationSessionSchema

- Temporarily disable the logic that adds the current user's ID to the collaboratorsIds array if not already included.
- This change is aimed at revisiting the collaboration session management without altering the existing functionality for customer role access.
This commit is contained in:
2024-11-30 23:12:34 +07:00
parent 2c38110183
commit bb56b7b61c

View File

@@ -88,17 +88,17 @@ export class CollaborationSessionSchema extends PothosSchema {
/* ---------- use case 1 : customer get collaboration session by id --------- */
if (ctx.http.me?.role === Role.CUSTOMER && collaborationSession) {
// if collaboratorsIds not include current user id, add it
if (!collaborationSession.collaboratorsIds.includes(ctx.http.me?.id)) {
collaborationSession.collaboratorsIds.push(ctx.http.me?.id)
await this.prisma.collaborationSession.update({
where: {
id: collaborationSession.id,
},
data: {
collaboratorsIds: collaborationSession.collaboratorsIds,
},
})
}
// if (!collaborationSession.collaboratorsIds.includes(ctx.http.me?.id)) {
// collaborationSession.collaboratorsIds.push(ctx.http.me?.id)
// await this.prisma.collaborationSession.update({
// where: {
// id: collaborationSession.id,
// },
// data: {
// collaboratorsIds: collaborationSession.collaboratorsIds,
// },
// })
// }
return collaborationSession
}
/* ---------- use case 2 : center mentor get collaboration session by schedule date id --------- */