We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jq 1.6 and master does not allow string input or argument
$ jq -n '1 | error' jq: error (at <unknown>) (not a string): 1 $ jq -n 'error(1)' jq: error (at <unknown>) (not a string): 1
gojq
$ ./gojq -n '1 | error' gojq: error: 1 $ ./gojq -n 'error(1)' gojq: error: 1
I kind of like that it's possible to throw non-string values and catch them. But maybe the difference should be documented?
The text was updated successfully, but these errors were encountered:
The exit code is same, and the behavior of gojq looks better. I think fixing it to type error does not change the behavior.
Sorry, something went wrong.
Agreeing, created a PR to document the difference.
Successfully merging a pull request may close this issue.
jq 1.6 and master does not allow string input or argument
gojq
I kind of like that it's possible to throw non-string values and catch them. But maybe the difference should be documented?
The text was updated successfully, but these errors were encountered: