-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
minItems not being respected in auto-generated example value #2076
Comments
Just verified it also happens in the live Swagger Editor: http://editor.swagger.io/ |
Got the same issue. It makes one have to manually add the missing values which slows down the work. Any updates on the issue? |
Thanks @GregNed for reminding me of this issue. I can confirm that both, the I can also confirm that the @GregNed maybe try updating your local Swagger component to latest? |
@hhromic Alright, let's close it then. I'm using it via the Connexion lib for Python. I guess they just haven't updated their dependencies yet. |
@GregNed looks like you are not alone: spec-first/connexion#1412 |
Q&A (please complete the following information)
latest
tag in Docker HubContent & configuration
Example OpenAPI definition:
Describe the bug you're encountering
The Swagger Editor is ignoring the
minItems
attribute of anarray
-type response when auto-generating example values. Currently, only one item is being generated regardless of theminItems
declaration in the schema.To reproduce...
Steps to reproduce the behavior:
/test
endpoint path and verify the example value being generated for the responseExpected behavior
Auto-generated example value showing at least
minItems
elements in the array. For the example in this issue, it should be showing something like this:[0, 0, 0]
.Screenshots
The text was updated successfully, but these errors were encountered: