When we export the api spec in openapi 3.0, no matter if we use web or client, we get a spec valid only in 3.1 spec, and not 3.0 spec.
May I ask if you can take a screenshot to see？
When I tell Apidog to export the 3.0 spec the header says 3.0.1 which is a minor patch to 3.0 and NOT the same thing as 3.1. Check your json to make sure it’s 3.0.1.
3.0.1 patch details can be found here: Release OAS 3.0.1 Released! · OAI/OpenAPI-Specification · GitHub
As for your error, the plural “examples” is allowed in OpenAPI 3.0 according to Smartbear/Swagger so it
https://swagger.io/docs/specification/adding-examples/
Can you show underlying JSON for those lines throwing the errors?
here for example
it is indeed exported as 3.0.1
it seems that to validate it, we should transform to “example” and change it from a list to a single value
Yeah… your first assumption seems to be correct, this is a bug as far as I can see (I’m glad I dug in as far as I did because I learned more about Apidog in the process).
Your contract is breaking because you have an “example” in your schema and it is being rendered as “examples” (I originally thought it was the example/examples in the path). OpenAPI 3.0.1 requires it to be singular, 3.1 suggests it be plural. I suggest you open this as a bug in the bug-report channel.
Keep in mind Openapi 3.0 DOES support “examples” in paths requests and responses.
will do! thanks