refactor(graphql-codegen): separate concerns by moving business logic to core

[pyramation]

refactor(graphql-codegen): separate concerns by moving business logic to core

Summary

Refactors the @constructive-io/graphql-codegen package to properly separate concerns by moving all business logic from the cli/ directory into a core/ directory structure. The CLI commands are now thin wrappers that handle user interaction while delegating to core modules.

Structural changes:

• cli/codegen/* → core/codegen/* (code generation)
• cli/introspect/* → core/introspect/* (schema introspection)
• cli/watch/* → core/watch/* (watch mode)
• cli/commands/shared.ts → core/pipeline/index.ts

New core modules:

• core/config/ - Config loading (loader.ts) and resolution (resolver.ts)
• core/output/ - File writing utilities (writer.ts)
• core/database/ - Database schema utilities (buildSchemaFromDatabase, buildSchemaSDLFromDatabase)
• core/introspect/source/database.ts - DatabaseSchemaSource for in-memory database introspection
• core/introspect/source/pgpm-module.ts - PgpmModuleSchemaSource for PGPM module introspection
• core/introspect/source/api-schemas.ts - Utilities for resolving schemas from API names
• core/codegen/shared/ - Shared types generator for unified output

Key pattern change: The watch orchestrator now accepts generate functions via dependency injection to avoid circular dependencies between CLI commands and core modules.

Updates since last revision

Phase 11: Database/PGPM config restructuring

Restructured the configuration to use a cleaner nested db object pattern:

• Renamed schema → schemaFile throughout codebase
• Consolidated pgpmModulePath, pgpmWorkspacePath, pgpmModuleName into nested db.pgpm object
• Moved schemas, apiNames, keepDb into the db object
• Added db.config?: Partial<PgConfig> with fallback to environment variables via getEnvOptions().pg
• Updated CLI to use --schema-file flag and new db structure
• Updated README with new config structure examples and programmatic API documentation
• Updated all tests for new config structure

New config structure:

await generate({
  db: {
    config: { host: 'localhost', database: 'mydb' }, // optional, falls back to env vars
    pgpm: { modulePath: './packages/my-module' },    // or workspacePath + moduleName
    schemas: ['public'],
    apiNames: ['my_api'],  // mutually exclusive with schemas
    keepDb: true,          // for debugging
  },
  output: './generated',
  reactQuery: true,
  orm: true,
});

Review & Testing Checklist for Human

• Test the new db config structure: Verify that db.pgpm.modulePath, db.schemas, db.apiNames, and db.config all work correctly at runtime
• Verify CLI flag changes: Test --schema-file (renamed from --schema), --pgpm-module-path, --schemas, --api-names flags
• Test environment variable fallback: When db.config is not provided, verify it correctly falls back to PGHOST, PGPORT, PGUSER, PGPASSWORD, PGDATABASE environment variables
• Verify README examples: The README was heavily rewritten - spot check that the code examples actually work
• Test multi-target config: Verify resolveConfigTargets() correctly handles the new nested db structure in defaults and targets

Notes

• All 193 unit tests pass in graphql-codegen, all 10 tests pass in packages/cli
• Build succeeds with TypeScript compilation
• All 48 CI checks pass
• Breaking changes:
  • schema config field renamed to schemaFile
  • database, pgpmModulePath, pgpmWorkspacePath, pgpmModuleName, schemas, apiNames, keepDb moved into nested db object
  • CLI flag --schema renamed to --schema-file
  • generateReactQuery and generateOrm are no longer exported - use generate({ reactQuery: true }) or generate({ orm: true })
  • ResolvedConfig, ResolvedWatchConfig, ResolvedQueryKeyConfig types are deleted - use GraphQLSDKConfigTarget, WatchConfig, QueryKeyConfig
• The generated ORM code in graphql-server is now static (committed) and no longer regenerated via devDependency

Link to Devin run: https://app.devin.ai/sessions/52a59f63cea74493bcb0d97f67422e8d
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