Support @file prefix for call --data#8
Open
sharoonthomas wants to merge 1 commit into
Open
Conversation
Accept '--data @payload.json' to read the JSON body from a file, matching the convention used by curl, gh, aws, and similar CLIs. Agents and scripts commonly generate larger payloads to a temp file rather than shell-escape them inline, and the previous behavior was to treat the literal string '@path' as JSON and fail with a confusing parse error. A literal value starting with '@' can still be passed by escaping as '\@literal'. Missing files surface a clear "Cannot read file" message instead of a JSON parse error. Scoped to 'model call --data' for now; --where and other JSON args are unchanged.
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.
Accept '--data @payload.json' to read the JSON body from a file, matching the convention used by curl, gh, aws, and similar CLIs. Agents and scripts commonly generate larger payloads to a temp file rather than shell-escape them inline, and the previous behavior was to treat the literal string '@path' as JSON and fail with a confusing parse error.
A literal value starting with '@' can still be passed by escaping as '@literal'. Missing files surface a clear "Cannot read file" message instead of a JSON parse error.
Scoped to 'model call --data' for now; --where and other JSON args are unchanged.