Tamp.GraphQLCodegen

graphql-code-generator CLI wrapper for Tamp.

Package	graphql-codegen	Status
Tamp.GraphQLCodegen.V5	5.x	preview

Requires Tamp.Core ≥ 1.0.3.

Why a separate repo

graphql-code-generator's CLI surface is small but its plugin ecosystem shifts independently. Per the satellite-repo convention, this tracks the codegen CLI's release cadence independently of tamp core.

Install

<PackageVersion Include="Tamp.GraphQLCodegen.V5" Version="0.1.0" />

<PackageReference Include="Tamp.GraphQLCodegen.V5" />

Verbs

Verb	Notes
Generate	The default invocation. --config, --overwrite, --watch [pattern], --project.
Init	Interactive scaffold.
Raw	Escape hatch for flag combinations we haven't typed.

Common flags (apply to every verb): --silent, --verbose, --debug, --errors-only, --profile, --require <module> (repeatable).

Quick example

using Tamp;
using Tamp.GraphQLCodegen.V5;

[NuGetPackage("graphql-codegen", UseSystemPath = true)]
readonly Tool Codegen = null!;

Target Codegen => _ => _.Executes(() =>
    GraphQLCodegen.Generate(Codegen, s => s
        .SetConfig("codegen.ts")
        .SetOverwrite()
        .SetWorkingDirectory(RootDirectory / "frontend")));

Test the wrapper itself

The integration tests stage a small schema + operation fixture in a temp dir and run graphql-codegen --config codegen.yml --silent against it. They expect graphql-codegen on PATH:

npm install -g @graphql-codegen/cli@5 graphql@16

Unit tests don't need any external tool — they verify CLI argument shape only.

Releasing

See MAINTAINERS.md.