Some schema validation fields are missing or not implemented according to the JSON schema validation specification (which is used in several parts of the OpenAPI 3.0 specification). This adds the missing fields and fixes the type of minimum, which may only take integers and not arbitrary schemas.
Notes
As the JSON schema validation specification only mentions that pattern “SHOULD” be a valid regular expression, I suggest representing it as a plain String.
Some schema validation fields are missing or not implemented according to the JSON schema validation specification (which is used in several parts of the OpenAPI 3.0 specification). This adds the missing fields and fixes the type of
minimum, which may only take integers and not arbitrary schemas.Notes
pattern“SHOULD” be a valid regular expression, I suggest representing it as a plainString.exclusiveMinimumandexclusiveMaximumfrom Boolean to integer. To comply with OpenAPI 3.0, we have to stick with Booleans for now.