-
Notifications
You must be signed in to change notification settings - Fork 220
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Migrate to OpenAPI 3.1 Implemented nullable schema and Ref supports `description` and `summary` fields now. `examples` field has been added to all schema objects. It is tested on structs. Complex enums do not directly support `examples` but the `examples` will directly render under the actual type object of a complex enum variant. Add support for deriving `content_encoding` and `content_media_type` on struct named fields. In OpenAPI 3.0 the request body and response body with type `string` and format `binary`, `byte`, `base64` was considered a `application/octet-stream`. However the OpenAPI 3.1 does not require such and and the schema can be completely ignored in such cases. This commit will remove the old behaviour where [u8] was rendered as `type: string` `format: binary` for recognizing `application/octet-stream`. From now on the content schema will be resolved as is which means that [u8] will be rendered as `type: array` of `items: int32`. Update documentation and add more known formats according to the https://datatracker.ietf.org/doc/html/draft-bhutton-json-schema-validation-00#section-7.3
- Loading branch information
Showing
23 changed files
with
1,194 additions
and
461 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.