feat: add schema-driven Tailcall configuration generator#627
Open
ameyypawar wants to merge 2 commits into
Open
feat: add schema-driven Tailcall configuration generator#627ameyypawar wants to merge 2 commits into
ameyypawar wants to merge 2 commits into
Conversation
Add a /app/config page that generates a Tailcall configuration from a form built dynamically from .tailcallrc.schema.json. Includes searchable dropdowns, live JSON/YAML/GraphQL output with copy and download, schema validation, and a Playground entry point. Implements tailcallhq#373.
Author
|
/claim #373 |
…the UI The live .tailcallrc.schema.json describes the runtime configuration (server, upstream, telemetry, links); realign the form, serializers, bundled fallback and tests to it. Emit runtime GraphQL as a schema extension, collapse single-value enum unions like LinkType into one dropdown, default to YAML, and restyle with a dark code-editor output panel.
ameyypawar
added a commit
to ameyypawar/tailcallhq.github.io
that referenced
this pull request
Jul 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
A Configuration Generator at
/app/configthat builds a Tailcall configuration through a form generated directly from.tailcallrc.schema.json, then exports it as YAML, JSON or GraphQL.The form is generated from the schema fetched at runtime, so it tracks schema changes automatically rather than hardcoding fields. Values drawn from a fixed set (HTTP version, link type, …) use searchable dropdowns, and the config is validated against the schema as you edit.
Preview
Scope: the runtime configuration
.tailcallrc.schema.jsondescribes Tailcall's runtime configuration —server,upstream,telemetryandlinks. In the v2 configuration split, types and resolvers (@http, etc.) live in a separate GraphQL schema config, so they are intentionally out of scope for this page: the tool builds exactly what the JSON schema defines, which is what keeps it genuinely schema-driven and correct as the schema evolves. A companion form for the GraphQL schema config is a natural follow-up.How it maps to #373
extend schema @server(...) @upstream(...)), which is what a runtime config is./playgroundto the generator, and a link back./app/configper Update 1.Trying it locally
then open
/app/config(and/playgroundfor the entry point).Tests
Adds a Cypress e2e spec covering schema loading, all three output formats, live editing and the export actions, with a fixture so the run is deterministic. No new dependencies are introduced.
Implements #373