Phil Sturgeon
Phil Sturgeon
Hello there! I've made an issue on https://github.com/thephpleague/openapi-psr7-validator/issues/163 to track progress towards OpenAPI v3.1, so give that a follow if you're interested. Perhaps you could help them out!
Hello! As the maintainer of [openapi.tools](https://openapi.tools), and as somebody works with Linux Foundation helping out in OpenAPI-land, I'm reaching out to tooling vendors to track the progress towards supporting OpenAPI...
Hello there! I'm making isues for all of the tools we've got listed on www.openapi.tools to see what folks are planning to do about OpenAPI v3.1.0 support. It's got some...
Much like openapi.tools, we should break this down by category
Make sure every post/put/delete/patch endpoint has some sort of securityScheme applied.
Let's get explicit about our charsets and not leave it up to guesswork or conflicting defaults but suggesting mime type should have `"; charset=utf-8` on the end, or at least...
Make sure the response object for any 200-299 response code does not contain any of the following properties: - errors - error - warnings - warning It should also not...
Good idea in https://apistylebook.stoplight.io/docs/url-guidelines to have `paths-no-file-extensions`. Let's make a rule for that. > Paths must not include json or xml file extensions.
``` format: oas3 ``` Parameter styles, full of powerful footguns which are luckily too confusing to operate. Doesn't look too confusing yet, but... **enhance!** Wait what? **enhance!** AAGGGH Ok, so...