You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
but without success, because the last "additionalProperties":false conflicts with the allOf. But the only way to "join" properties is via allOf. Keep in mind that omitting "additionalProperties":false leads to the appearance of the + new button in jsonary...
Please help...
The text was updated successfully, but these errors were encountered:
"additionalProperties":false is evaluated against the property definitions in properties/patternProperties.
In your second example, only "c" and "d" are defined, so according to the schema, "a" and "b" are not allowed. You'll need stub entries (e.g. "a":{}, "b":{}) to keep them permitted.
Perhaps there should be some kind of flag you could set, that removed the + new option from all objects unless additionalProperties was explicitly set to true...
are you planning something new in v5? I've seen that someone was suggesting a patch possibility?
Stub entries are no solution for me, maybe the flag (Jsonary property) solution ...
I want to to have a resulting schema like:
but
"a"
and"b"
shall be defined via a"$ref"
among many other things I tried was:
but without success, because the last
"additionalProperties":false
conflicts with theallOf
. But the only way to "join" properties is viaallOf
. Keep in mind that omitting"additionalProperties":false
leads to the appearance of the+ new
button in jsonary...Please help...
The text was updated successfully, but these errors were encountered: