Will Smith

This was completed in #423; closing this branch

It looks like, as of OpenAPI 3.1.0, the Reference Object was updated to include optional `summary` and `description` fields: [3.1.0 Reference Object](https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#reference-object) vs [3.0.0 Reference Object](https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.0.0.md#reference-object) definition. I must've missed...

It absolutely is; those are called "extensions" and you can read the above ones like so: ``` dorthu@travel-dev:~/source/openapi3$ cat example.yaml openapi: "3.1.0" info: paths: components: schemas: User: properties: userId: type:...

It sounds like you're on the right track; I'd add a new condition [in here](https://github.com/Dorthu/openapi3/blob/f0bf96a850a66c50c4f93b3633b2d0a3c9f890b1/openapi3/paths.py#L270-L284) to hande `multipart/form-data` requestBody types; the incoming data type will also matter, as a valid...

Reading it over, this looks good - I hadn't considered before the possibility that a request would have a regular body and a set of files, but having the fields...

This will not pass validation without https://github.com/Dorthu/openapi3/pull/48, as these fields were previously not included in the parser/validator.