Remove BOM from JSON schemas #415
Description
I'm submitting a ...
- bug report
- feature request
- support request => Please do not submit support request here, see note at the top of this template.
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.