fix(builtins): produce empty JSON string for jq -Rs with empty stdin#971
Merged
fix(builtins): produce empty JSON string for jq -Rs with empty stdin#971
Conversation
When -R (raw input) and -s (slurp) are combined, empty stdin should produce "" (empty JSON string), not no output. Removed early return that skipped output when input was empty. Closes #952
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.
Summary
jq -Rs '.'producing no output on empty stdin instead of""input.trim().is_empty()fired before the-Rscode path could create an empty string value&& !(raw_input && slurp)guard so-Rswith empty stdin proceeds to createVal::from("")Test plan
jq_raw_slurp_empty_stdin— verifiesprintf '' | jq -Rs '.'outputs""jq_raw_slurp_normal— regression test for non-empty inputCloses #952