Peter Van den Bosch
Peter Van den Bosch
> I assume the https://www.belgif.be/specification/rest/api-guide/#rule-oas-contra rule will be updated to require OpenAPI 3.0? I'll propose something like "new APIs should use OpenAPI 3.0". > So a Swagger 2.0 contract is...
rest-guide-validator: WG prefers to make configurable to fail on OpenAPI 2.0 fail, default is then to fail. Configurable with skipOnError.
When testing one of the examples with oneOf of two object subschemas, I noticed that it's missing `required` properties to make the subschemas non-overlapping: ```YAML OneOfTwoObjects: type: object oneOf: -...
for the example "Making a property of another schema required", validation of the property being required doesn't seem to work (using swagger-request-validator 2.46.0, couldn't get it to work in v2.44.1...
REST WG is OK that oneOf with object type subschemas shouldn't be used. We can add the swagger-request-validator buggy behavior in the example, but not in the rule bc it...
PR created. restricts allowed usage to: * subschemas without a type constraint that only list required properties * subschemas with an enum of a simple type (i.e. no array or...
REST guide WG: * guideline on OpenAPI/AsyncAPI is OK, but more clearly explain grouping of event definitions using single entry document * merging will wait on remaining discussion on CloudEventBase...
REST guide WG reviewed PR, OK to merge and publish.