feat: add Tailcall config generator - #626
Closed
rohitmulani63-ops wants to merge 1 commit into
Closed
Conversation
Author
|
Hi, just checking if anything else is needed on this. I can adjust the generator docs or examples if you want any changes. |
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. |
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
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.
Closes #373
/claim #373
Summary
I added a focused Tailcall config generator at
/app/config.What changed:
.tailcallrc.schema.jsondynamically from the generated Tailcall schema URLI kept the PR intentionally small and reviewable.
Validation
CYPRESS_INSTALL_BINARY=0 npm cipassednpm run buildpassed and generated the production static filesgit diff --checkpassed, with only normal Windows line-ending warningsnpm run start -- --host 127.0.0.1 --port 3063compiled the client successfully in local dev modeNotes:
npm run typecheckcurrently fails on existing unrelated repo issues inpublish-externals,Playground.tsx, and the custom DocSearch theme fileswspackages (bufferutil,utf-8-validate) and stale Browserslist data