Ignore filters in affected entity check (#3366)

Co-authored-by: Niko Sams <ns@vivid-planet.com> Co-authored-by: Johannes Obermair <48853629+johnnyomair@users.noreply.github.com>
vivid-planet · Feb 11, 2025 · a84d88c · a84d88c
1 parent e7b49d3
commit a84d88c
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 1 deletion.
diff --git a/.changeset/eighty-goats-beam.md b/.changeset/eighty-goats-beam.md
@@ -0,0 +1,7 @@
+---
+"@comet/cms-api": minor
+---
+
+Ignore filters in `@AffectedEntity` check
+
+When using the `@AffectedEntity` decorator we possibly also want to check entities which are filtered by default. Since we don't know how the entity is handled in the resolver we ignore the filters completely.
diff --git a/packages/api/cms-api/src/user-permissions/content-scope.service.ts b/packages/api/cms-api/src/user-permissions/content-scope.service.ts
@@ -82,7 +82,7 @@ export class ContentScopeService {
                 }
 
                 for (const id of ids) {
-                    const row = await repo.findOneOrFail(id);
+                    const row = await repo.findOneOrFail(id, { filters: false }); // disable all default filters, e.g., excludeDeleted
                     if (row.scope) {
                         contentScopes.push([row.scope as ContentScope]);
                     } else {