Fix minor swagger inconsistencies #520
Merged
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
gmelodie
force-pushed
the
gabe/swagger-tidy
branch
from
fc68a32
to
be99d1b
Compare
gmelodie
force-pushed
the
gabe/swagger-tidy
branch
from
90e57a0
to
3ffdf66
Compare
alvin-reyes
reviewed
Nov 11, 2022
|
@gmelodie any update on this? |
|
@alvin-reyes @snissn @gmelodie let's get this in |
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.
I found a couple inconsistencies on our swagger annotations:
pathvariables not being required@Param bodys (which is not allowed)/admin/peeringwas a subgroup but we don't do that on other admin subgroups like/admin/cmpeering,peerstags from/admin/peeringendpoints (cause them to show up duplicated on swagger)