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
When parsing a JSON file with BOM such as:
https://github.com/dotnet/toolset/blob/40cc5860e2ef311b9aca733b1d2eccaa681bd422/TestAssets/InstallationScriptTests/InstallationScriptTests.json
JSON.sh gives the following error:
EXPECTED EOF GOT {
Current workaround is to strip these characters using tool like awk: awk 'NR==1{sub(/^\xef\xbb\xbf/,"")}1' "$json_file" | sh JSON.sh | .....
awk 'NR==1{sub(/^\xef\xbb\xbf/,"")}1' "$json_file" | sh JSON.sh | ....
It would be nice if parser skip these BOM characters and start parsing after the offset. It will save consumers from stripping these characters.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When parsing a JSON file with BOM such as:
https://github.com/dotnet/toolset/blob/40cc5860e2ef311b9aca733b1d2eccaa681bd422/TestAssets/InstallationScriptTests/InstallationScriptTests.json
JSON.sh gives the following error:
EXPECTED EOF GOT {Current workaround is to strip these characters using tool like awk:
awk 'NR==1{sub(/^\xef\xbb\xbf/,"")}1' "$json_file" | sh JSON.sh | .....It would be nice if parser skip these BOM characters and start parsing after the offset. It will save consumers from stripping these characters.
The text was updated successfully, but these errors were encountered: