chore(tooling): move GraphQL schema to apps/cms, remove packages/contracts#57
chore(tooling): move GraphQL schema to apps/cms, remove packages/contracts#57
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
….graphql Co-authored-by: Cursor <cursoragent@cursor.com>
|
Caution Review failedThe pull request is closed. WalkthroughRemoves Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
AGENTS.md (2)
48-48:⚠️ Potential issue | 🟡 MinorStale "contracts" language in agent operating rules.
The rule "If contracts change: regenerate clients in same PR" should reference the schema since there is no longer a contracts package.
📝 Suggested fix
- - If contracts change: regenerate clients in same PR. + - If the GraphQL schema (`apps/cms/schema.graphql`) changes: regenerate clients in same PR.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@AGENTS.md` at line 48, Update the stale rule text "If contracts change: regenerate clients in same PR" to reference the schema instead; replace it with something like "If schema changes: regenerate clients in the same PR" (or similar wording) so the agent operating rules use "schema" rather than the obsolete "contracts" terminology and ensure any related bullet/heading that mentions contracts is updated to the word "schema".
9-9:⚠️ Potential issue | 🟡 MinorAmbiguous "Contracts" reference in non-negotiable invariants.
packages/contractsno longer exists, so line 9 is opaque to agents unfamiliar with the history. The intent is thatapps/cms/schema.graphqlis the authoritative source of truth for integrations.📝 Suggested fix
- - Contracts are source of truth for integrations. + - `apps/cms/schema.graphql` is source of truth for integrations.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@AGENTS.md` at line 9, Replace the ambiguous reference "Contracts are source of truth for integrations." with an explicit pointer to the current authoritative schema by updating the line in AGENTS.md to say that apps/cms/schema.graphql is the source of truth for integrations (e.g., "The authoritative schema for integrations is apps/cms/schema.graphql"). Ensure the wording mentions the file path apps/cms/schema.graphql so new agents can locate the schema without historical context.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@packages/README.md`:
- Line 3: Update the README header to remove the stale reference to "contracts":
find the header string "Shared contracts, generated clients, models, AI config,
and codegen tooling." in packages/README.md and edit it to something like
"Shared generated clients, models, AI config, and codegen tooling." so it no
longer mentions the deleted packages/contracts.
---
Outside diff comments:
In `@AGENTS.md`:
- Line 48: Update the stale rule text "If contracts change: regenerate clients
in same PR" to reference the schema instead; replace it with something like "If
schema changes: regenerate clients in the same PR" (or similar wording) so the
agent operating rules use "schema" rather than the obsolete "contracts"
terminology and ensure any related bullet/heading that mentions contracts is
updated to the word "schema".
- Line 9: Replace the ambiguous reference "Contracts are source of truth for
integrations." with an explicit pointer to the current authoritative schema by
updating the line in AGENTS.md to say that apps/cms/schema.graphql is the source
of truth for integrations (e.g., "The authoritative schema for integrations is
apps/cms/schema.graphql"). Ensure the wording mentions the file path
apps/cms/schema.graphql so new agents can locate the schema without historical
context.
Co-authored-by: Cursor <cursoragent@cursor.com>
Review feedback addressed (12240f6)Fixed:
|
Resolves #56
Summary
Move GraphQL schema from packages/contracts to apps/cms/schema.graphql. Schema is auto-generated by Strapi; packages/contracts and validate-contracts were redundant.
Contracts Changed
Regeneration Required
Validation
Summary by CodeRabbit
Chores
New Features
Documentation