top | item 34593563

(no title)

relequestual | 3 years ago

Actually, currently, this is not the case. The specification explicitly allows for additional fields for the purposes of extensions. We are considering changing that, and only allowing pre-defined fields, or having a way to mark specific fields as limited extensions.

discuss

order

Taywee|3 years ago

Huh, you're right. There is additionalProperties, but I mistakenly thought `"additionalProperties": false` was the default.

relequestual|3 years ago

It is not =]

Additionally, the value is a "schema" as opposed to a boolean, meaning you can apply a subschema to any additional fields. Useful if you for instance want to make sure any additional fields start with a specific prefix.

Booleans are valid schemas. It's subschemas all the way down! I wrote an article around this topic: https://json-schema.org/blog/posts/applicability-json-schema...