JSON Schema Override in Attribute Object
stupid question incoming
...
Is it intentional that when a new
I have an example:
I would have expected the intersections of non-overlapping records?
for example, in the case of the
But maybe the the issue lies in the
Is it intentional that when a new
jsonSchema attribute gets attached to the attribute obj, said jsonSchema completely override the existing properties? I have an example:
I would have expected the intersections of non-overlapping records?
for example, in the case of the
minLength filter, which power the NonEmpty string constructor, it could be done like this, right?But maybe the the issue lies in the
export type JSONSchemaAnnotation = object , as it allows an arbitrary nested structure...