Research why the default validation method didn't catch errors in the example schema #66
Assignees
Labels
Comments
tobywf
added a commit
that referenced
this issue
Oct 25, 2018
This is inefficient when only one item from a large schema is inlined, but this way inlined schemas are still valid (my previous way of flattening refs included `/` in the property names). Schemas are inlined under a reserved "remote" property at the same level of "definitions" and "properties". As a side effect, RefRenamer no longer has to worry about clobbering keys, so that code was simplified. Had to fix example schemas - need to do more research on why this wasn't caught earlier (#66).
|
Need to either resolve refs before we validate (issue with circular refs?), or set up the metaschema/schema/data dynamic correctly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The RefInliner change of #56 exposed some errors in the example schemas. Why were these not caught using the normal validation method? Did we set it up wrong, so it doesn't do recursive validation?
The text was updated successfully, but these errors were encountered: