11578 mark swagger available- apis to accept lists in post #13445
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
arthanson
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixes: #11578
Marks the available APIs as returning a list. The technically correct fix would be using a PolymorphicProxySerializer as these can be called with a single object or a list, however this would cause the swagger to emit a "oneOf" which is not supported in Go OpenAPI generator, also it makes the spec more complex. If you only have to request a single item, just use a list with a single object as request so there really isn't a downside for this.
@jeremystretch I was mistaken, these only effect the availalbe-api's so there weren't that many to change.