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 and gojq handle leading 0s differently. Has this been documented?
$ gojq . <<< 0862 0 862 $ jq . <<< 0862 jq . <<< 0862 862 $
This is definitely worth noting because gojq is somewhat inconsistent in its treatment of leading 0s:
$ gojq -n 0862 862
The text was updated successfully, but these errors were encountered:
This is considered as the instance of difference on the JSON parser strictness. I don't like the jq behavior handles invalid JSONs.
Sorry, something went wrong.
0d2a8cc
@itchyny wrote:
This is considered as the instance of difference on the JSON parser strictness.
OK, but I don't see anything about this in the "Difference to jq" section.
Also, is gojq's internal inconsistency noted? Or should that be the subject of a bug report?
There is no inconsistency because jq query and JSON have different syntax.
No branches or pull requests
jq and gojq handle leading 0s differently. Has this been documented?
This is definitely worth noting because gojq is somewhat inconsistent in its treatment of leading 0s:
The text was updated successfully, but these errors were encountered: