Mergekeys not allowed when JSON schema's are used
See original GitHub issueWhen validating a YAML file with a JSON schema like this:
{
"type": "object",
"properties": {
"prop1": {
"type": "string"
},
"prop2": {
"type": "string"
}
},
"additionalProperties": false,
"required": [
"prop1"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}
It is not possible to use merge keys, it says that ‘<<’ is not a valid property:
Would it be possible to ignore ‘<<’ properties when validating schema’s?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:6
- Comments:8 (5 by maintainers)
Top Results From Across the Web
YAML Anchor, Aliases and Merge Keys
Some of YAML's properties not in JSON are anchors, aliases and merge keys that can work well together. These allow references and mixins...
Read more >object — Understanding JSON Schema 2020-12 ...
Setting the additionalProperties schema to false means no additional properties will be allowed.
Read more >XSL Transformations (XSLT) Version 3.0
[ERR XTSE0010] It is a static error if an XSLT-defined element is used in a context where it is not permitted, if a...
Read more >Only allow properties that are declared in JSON schema
For instance if a user passes a "name" property in their json object it will fail this schema because "name" is not listed...
Read more >JSON Schema Serializer and Deserializer
In order to allow the JSON Schema deserializer to work with topics with ... on the JSON Schema that specifies the fully-qualified Java...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think I have a fix for this that should make it into the next release, when I was switching everything from using a JSON 4 parser to a JSON 7 parser I missed a part of code that processes merge keys correctly
The new version has been released so I’m closing.