-
Notifications
You must be signed in to change notification settings - Fork 839
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
OpenAPI/Swagger schemas with >2 example objects fail to import into Postman properly #9344
Comments
@amroczeK Thanks for reporting the issue, We have identified the issue and will be working on fixing it. We will keep this thread updated with all developments. |
No worries, keep up the great work! |
We are excited about this improvement as well. Looks like it is up 'Next' in the development cycle based on the last notification here. |
This should now be resolved. Can you verify that this is working for you in the most recent version of the app? |
Confirmed! It is working now!
…On Thu, Apr 15, 2021, 6:45 AM Trent M ***@***.***> wrote:
This should now be resolved. Can you verify that this is working for you
in the most recent version of the app?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#9344 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AM2QGWC6LS6IFEMFN6JYDBDTI27UHANCNFSM4UPNNUMQ>
.
|
Great work guys, it's working :) |
I have been banging my head against the table trying to figure out why schemas with an array of objects that have multiple object examples in swagger aren't importing properly into POSTMAN when you have more than 2 examples.
Everything looks fine in https://editor.swagger.io/ and in the served swagger file on website application, but the same result isn't shown in POSTMAN.
Also raised with swagger swagger-api/swagger.io-docs#293
Swagger example:
These are the results of importing the swagger doc into POSTMAN:
/test1 API body:
/test2 API body:
Result after reducing the example objects to only 2 for /test2 API:
The text was updated successfully, but these errors were encountered: