changes for #2054 - extension fields in info.contact do not propagate… #2171
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
… propagate to embedded spec
… propagate to embedded spec Signed-off-by: Amruta Kulkarni <amruta9.kulkarni@gmail.com>
casualjim
approved these changes
Jan 26, 2020
|
@kul-amr thanks for your contribution. I think we have fixed our CI issues: you may rebase and PGP-sign you commit. This should be good to go. |
|
looks like those fields are missing from the spec repo |
|
@casualjim I had added the fields in spec and have created a pull request go-openapi/spec#113 |
This was referenced Feb 3, 2020
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.
This is a bug fix for #2054. This fix will include extension/custom fields from Contact and License to the spec served by the generated server.