Fix full schemas #77
Fix full schemas #77
Conversation
| html: '<audio></audio>' | ||
| - | ||
| _valid: false | ||
| _name: "valid-audio-without-type" |
There was a problem hiding this comment.
Why remove these testcases?
There was a problem hiding this comment.
Seems they were moved into contentblock.yml
There was a problem hiding this comment.
Moved from here to contentblock since after dereferencing they need the full content block definition for validation to work correctly
| src: | ||
| "$ref": "contentblock.json#/definitions/src" | ||
| description: Block type | ||
| example: "text" |
There was a problem hiding this comment.
The example says "text", but only valid in the enum is article ?
| src: | ||
| "$ref": "contentblock.json#/definitions/src" | ||
| description: Block type | ||
| example: "text" |
|
@bergie this means that one should never use the individual block schemas right, as they are not complete? For instance |
|
Well, the JSON needs to be build so |
|
@jonnor good to go? |
|
@bergie deploy at will |
Currently our full schemas are broken due to circular references in
contentblock. This makes JSON schema derefencing failures fatal, and fixes the contentblock->specific type circular refs