Support marshmallow Tuple field (#399)#1045
Closed
SAY-5 wants to merge 2 commits into
Closed
Conversation
Member
|
would rather see this feature implemented by an actual user of apispec rather than an agent strafing github for cred... |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Adds OpenAPI conversion for the marshmallow
Tuplefield, which was requested in #399 ("Yes! Absolutely. Would you like to submit the change?"). The fixed-length contained fields are described withprefixItemson OpenAPI 3.1 and withitems/oneOfon earlier versions, andminItems/maxItemsare set to the tuple length. Closes #399.