cms-api: Validate PageTreeNode scope DTO name in PageTreeModule

[VPS-Obi]

Description

PageTreeNodeScope/PageTreeNodeScopeInput are the fixed GraphQL type names a project-specific PageTreeNode scope class must use — a comment in demo/api/src/page-tree/dto/page-tree-node-scope.ts even calls this out ("name must not be changed in the app"). Nothing enforced it though, so an accidental rename would only surface later as a confusing runtime GraphQL schema error, instead of failing fast with a clear message.

DamModule already has this exact safeguard for its own Scope option (validating against "DamScope"/"DamScopeInput"). This PR adds the equivalent check to PageTreeModule.forRoot().

Solution

In packages/api/cms-api/src/page-tree/page-tree.module.ts, after resolver generation (so the input type metadata is available) and before building providers, validate that a provided Scope class is decorated with @ObjectType("PageTreeNodeScope") and @InputType("PageTreeNodeScopeInput") via TypeMetadataStorage, throwing a descriptive error otherwise — mirroring DamModule.register().

Example usage

If a project's custom scope class is decorated with the wrong GraphQL type name, e.g.:

@ObjectType("MyScope") // wrong, should be "PageTreeNodeScope"
@InputType("MyScopeInput")
export class MyPageTreeNodeScope { ... }

PageTreeModule.forRoot({ Scope: MyPageTreeNodeScope, ... }) now throws at startup:

Error: Invalid object type name for provided page tree scope class. Make sure to decorate the class with @ObjectType("PageTreeNodeScope")

instead of failing later with an opaque GraphQL schema error.

Further information

• No existing tests cover DamModule's equivalent validation, so no new test was added here either, to stay consistent.
• Closes Add page tree node scope DTO name validation #6172

---

Generated by Claude Code

[VPS-Obi]

We should remove the TODO from Demo then.

[VPS-Obi]

Good call — pushed 7231a84 removing the TODO from demo/api/src/page-tree/dto/page-tree-node-scope.ts. The validation now added to PageTreeModule covers the concern it was flagging.

---

Generated by Claude Code

[VPS-Obi]

Since we now validate this, we can remove the comments as well.

[VPS-Obi]

Pushed a59ca2e removing the // name must not be changed in the app comments — the PageTreeModule validation now enforces this at startup.

---

Generated by Claude Code

[VPS-Obi]

Pushed 0da79f0 adding unit tests for the scope validation, covering:

• a valid scope (correct @ObjectType/@InputType names) → no throw
• a scope with the wrong object type name → throws with the expected message
• a scope with the wrong input type name → throws with the expected message

One implementation note: @InputType() only queues its metadata for the schema builder and it isn't available via TypeMetadataStorage.getInputTypeMetadataByTarget() until a GraphQL schema is actually built (confirmed this empirically — even the real DamScope/PageTreeNodeScope classes show undefined there immediately after decoration). To keep the tests synchronous and independent of schema building, they register the input type metadata directly via TypeMetadataStorage.addInputTypeMetadata() instead of relying on @InputType()'s lazy registration — documented with a comment in the test file.

All 472 existing tests in @comet/cms-api still pass.

---

Generated by Claude Code