Fix zod typing for variables definition #29
Conversation
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
The query variables zod definition currently tells the LLM that it expects a string, which the LLM interprets as needing to be a JSON string. This will cause requests to fail, and then the LLM needs to figure out how to fix, which it does some of the time. By properly changing this to a zod record object, it allows the LLM to format the variables correctly the first time.
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.
The "query-graphql" tool's variables zod definition currently tells the LLM that it expects a string, which the LLM interprets as needing to be a JSON string. This will cause requests to fail, and then the LLM needs to figure out how to fix, which it does some of the time. By properly changing this to a zod record object, it allows the LLM to format the variables correctly the first time.
This will fix issue #26