We rely heavily on oneOf, allOf, etc. These are largely not compatible with additionalProperties=false. This is a problem as this json schema feature makes for safer apis and more useful validation results (prevents accepting typos in propery names for example).
I need to study the tricks that exist to manage complex cases while still using additionalProperties=false (like defining properties on the root and simply change the "required" attribute of subschemas ?) and improve vjsf compatibility with these cases.
We rely heavily on oneOf, allOf, etc. These are largely not compatible with additionalProperties=false. This is a problem as this json schema feature makes for safer apis and more useful validation results (prevents accepting typos in propery names for example).
I need to study the tricks that exist to manage complex cases while still using additionalProperties=false (like defining properties on the root and simply change the "required" attribute of subschemas ?) and improve vjsf compatibility with these cases.