refactor(graphql-codegen): use deepmerge for config merging

[pyramation]

Summary

Refactors the GraphQL codegen configuration system to use deepmerge instead of manual property-by-property merging. This aligns with patterns used elsewhere in the codebase (@pgpmjs/env, @constructive-io/graphql-env, supabase-test).

Key changes:

• Added deepmerge dependency
• Replaced ~80 lines of manual merge logic in mergeConfig with a single deepmerge call
• Simplified resolveConfig to just return the deepmerge result directly
• Updated DEFAULT_CONFIG to be a complete ResolvedConfig (includes endpoint: '' and schema: null)
• Uses array replacement strategy (source wins) to ensure include: ['users'] replaces ['*'] rather than merging to ['*', 'users']
• Added systemExclude field for tables, queries, and mutations to always exclude certain items (e.g., ['_meta', 'query'] for queries) while allowing users to override with systemExclude: [] if needed

Updates since last revision

• Renamed command functions for clarity:
  • generateCommand → generateReactQuery
  • generateOrmCommand → generateOrm
• Added enabled property to both ORM and React Query configs, both defaulting to false
• Simplified ORM handling: ORM config is no longer nullable - it's always an object with enabled: boolean, output: string, useSharedTypes: boolean
• Simplified resolveConfig: Now just a single deepmerge call with no special ORM handling needed:

  return deepmerge(DEFAULT_CONFIG, config, { arrayMerge: replaceArrays }) as ResolvedConfig;

• Updated packages/cli: The main CLI package (@constructive-io/cli) and its tests were updated to use the renamed functions

Review & Testing Checklist for Human

• IMPORTANT: Verify enabled properties are wired up: The types for config.reactQuery.enabled and config.orm.enabled were added, but verify the generation logic actually checks these flags before generating code. The diff shows type changes but the actual conditional logic may need to be added.
• Breaking change awareness: The function renames (generateCommand → generateReactQuery, generateOrmCommand → generateOrm) and reactQuery.enabled defaulting to false are breaking changes for external consumers
• Verify systemExclude behavior: Test that queries.systemExclude: ['_meta', 'query'] is applied by default, and that setting exclude: ['myQuery'] doesn't remove the system excludes
• Verify array replacement behavior: Test that specifying include: ['users'] in a config correctly replaces the default ['*']

Recommended test plan:

1. Run pnpm test in graphql/codegen (193 tests should pass)
2. Try generating code with a config that sets queries: { exclude: ['myQuery'] } and verify _meta and query are still excluded (via systemExclude)
3. Test with queries: { systemExclude: [] } to verify system excludes can be disabled
4. Verify that setting reactQuery: { enabled: true } or orm: { enabled: true } produces the expected output

Notes

• The large pnpm-lock.yaml diff is formatting changes only (pnpm version differences), not actual dependency changes
• ORM config is now always an object (never null), with enabled: false by default
• The as ResolvedConfig type assertion in resolveConfig is used because deepmerge returns a generic type

Link to Devin run: https://app.devin.ai/sessions/74f133230ae248f2a93a26ccf17cec43
Requested by: Dan Lynch (@pyramation)

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[mohamedbouddi7777-dev]

يحاول ان اتفهم يعني سهل الاعمال لان عندي عمل كثيره لا اقدر ان اشتغل على كل شيء يعني سهل الامور اريد الاداره