This repository was archived by the owner on Jun 20, 2024. It is now read-only.
Add vendor extensions support for fields. #190
Conversation
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
This PR adds support for "vendor extensions" option on a field level.
This allows to specify some additional metadata that can be passed to generated json-schemas. Especially, this is a powerful feature in case generated json-schemas referenced in OpenAPI specification which is used to generate client / server with openapi-generator.
In this case we can easily add support, for example, of validation rules by adding such vendor extension to any field: OpenAPITools/openapi-generator#1145
@chrusty please review