Release: v0.7.1 #59
Merged
Release: v0.7.1 #59
Conversation
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
The JSON result this processor outputs is compliant to the OpenAPI 3.0 spec, which is not restrictive to the Swagger platform. I think the naming of the processor should reflect this fact.
Rename Swagger processor to OpenAPI
1. Add support for more OpenAPI string formats. When we encounter a schema or paremeter field like `type: <format>` where the format is a valid OpenAPI string format, the docs output will become `type: "string", format: <format>". 2. Support list field shorthand for schema fields (we already do this for schemas used in responses and request bodies).
sjkaliski
approved these changes
Jun 3, 2019
Field formatting updates
Version Bump: v0.7.1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Processors.Swagger->Processors.OpenAPI(Rename Swagger processor to OpenAPI #58)