3 people b043eb3f60 fix(notification-trigger): seed default collaborators onto the parent doc, not the attached tx (#10975) ...

getCollaborators resolved the default collaborators of the parent doc (loaded via the triggering tx's attachedTo/attachedToClass) but seeded them onto tx.objectId — the attached child item (a comment/message create/update/remove tx). The parent's collaborators therefore landed on the child record instead of the parent.

Seed onto doc._id/doc._class/doc.space instead. Same class of bug as the chunter seed-target fix. The returned collaborator list is unchanged; only the target of the newly created Collaborator records changes.

Adds a unit test that drives getCollaborators directly: real getAddCollaboratTxes/getDocCollaborators, only getClassCollaborators stubbed. Parent and child are given distinct collaborators and spaces; it asserts the seed targets the parent (attachedTo/attachedToClass/objectSpace), never the child, while the returned collaborator list stays identical.

Signed-off-by: Michael Uray <michaeluray@users.noreply.github.com>
Co-authored-by: Michael Uray <michaeluray@users.noreply.github.com>

2026-09-25 18:41:22 +02:00

..

config

:Apply templates (#3799)

2023-10-07 16:38:21 +06:00

src

fix(notification-trigger): seed default collaborators onto the parent doc, not the attached tx (#10975)

2026-09-25 18:41:22 +02:00

.eslintrc.js

:Apply templates (#3799)

2023-10-07 16:38:21 +06:00

.npmignore

Send email notification when mentioned (#1031)

2022-02-22 16:09:13 +07:00

jest.config.js

:Apply templates (#3799)

2023-10-07 16:38:21 +06:00

package.json

Sync with foundations packages (#10703)

2026-03-31 10:23:56 +07:00

tsconfig.json

Fix ts-config to fix ts-server (#9019)

2025-05-22 17:22:04 +07:00