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
The UTF-8 byte order marks are present in JSON schemas (e.g., in allureConfig.schema.json).
According to RFC 8259 there shouldn't be any BOM at the beginning of a JSON document loaded remotely.
Some editors (e.g., VSCode) complains about the spec violations.
The text was updated successfully, but these errors were encountered:
delatrie
Successfully merging a pull request may close this issue.
I'm submitting a ...
What is the current behavior?
The UTF-8 byte order marks are present in JSON schemas (e.g., in allureConfig.schema.json).
What is the expected behavior?
According to RFC 8259 there shouldn't be any BOM at the beginning of a JSON document loaded remotely.
What is the motivation / use case for changing the behavior?
Some editors (e.g., VSCode) complains about the spec violations.
The text was updated successfully, but these errors were encountered: