Skip to content

feat: add Tailcall config generator - #626

Closed
rohitmulani63-ops wants to merge 1 commit into
tailcallhq:developfrom
rohitmulani63-ops:rohit/config-generator-clean
Closed

feat: add Tailcall config generator#626
rohitmulani63-ops wants to merge 1 commit into
tailcallhq:developfrom
rohitmulani63-ops:rohit/config-generator-clean

Conversation

@rohitmulani63-ops

@rohitmulani63-ops rohitmulani63-ops commented Jun 22, 2026

Copy link
Copy Markdown

Closes #373
/claim #373

Summary

I added a focused Tailcall config generator at /app/config.

What changed:

  • added a new schema-driven config generator page
  • loads .tailcallrc.schema.json dynamically from the generated Tailcall schema URL
  • lets users search and add schema fields instead of guessing field names
  • supports nested object fields, enum datalist inputs, booleans, numbers, arrays, and strings
  • provides JSON and YAML output downloads
  • includes a limited GraphQL preview for schema-level scalar directive values

I kept the PR intentionally small and reviewable.

Validation

  • CYPRESS_INSTALL_BINARY=0 npm ci passed
  • npm run build passed and generated the production static files
  • git diff --check passed, with only normal Windows line-ending warnings
  • checked the changed files for hidden/bidirectional control characters: clean
  • npm run start -- --host 127.0.0.1 --port 3063 compiled the client successfully in local dev mode

Notes:

  • npm run typecheck currently fails on existing unrelated repo issues in publish-externals, Playground.tsx, and the custom DocSearch theme files
  • the production build completed with existing non-fatal dependency warnings for optional ws packages (bufferutil, utf-8-validate) and stale Browserslist data

@rohitmulani63-ops

Copy link
Copy Markdown
Author

Hi, just checking if anything else is needed on this. I can adjust the generator docs or examples if you want any changes.

@rohitmulani63-ops

Copy link
Copy Markdown
Author

Thanks for the update. I saw #373 and this PR were closed today. Was the config generator direction dropped, or is there a newer preferred scope? If there is a specific gap worth carrying forward, I'm happy to adapt the work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feature: design and develop a UI to generate tailcall configurations

2 participants