Vishal Shingala

@vhawk19 WIP PR is open at https://github.com/postmanlabs/openapi-to-postman/pull/159, You can create separate PR or use that as reference PR for contribution.

@kzmKZuzmo Would you be able to share the Swagger schema/definition in question? We're not able to reproduce it at the moment so it'd help us out in reproducing the issue.

@sciamano89 Thanks for reporting the issue, we have identified it and are working on a fix.

@bruno-xo7 Unfortunately we don't support vendor extensions in security schema yet. so converted collection will contain Authorization set as `API Key` at the collection level.

Hey @philsturgeon, Thanks for reaching out! We already have added support for OpenAPI v3.1.0 for our existing functional APIs (i.e. converting OpenAPI 3.1 definition to Postman collection, validating the collection...

@thim81 It's fully backward compatible. We've designed the support for OpenAPI 3.1 keeping existing flows and code being the same and have created separate or reuse existing components so OpenAPI...

@khazamov Could you possibly share your specification or modified and shrunk version that can produce the same error? Looking at the schema you mentioned by you, it contains another reference...

@schneivo77 We have changed behaviour of how values are resolved for `example` option. Where if schema defined example is invalid or not available then instead generating string placeholders like `""`...

@michaelcilibrasi Can you explain more about your use case here? As any present responses in the collection will not affect anything in request so is there any valid reason to...

@dawn-stripe You can ignore `_` field here. It's identical to one present at `info._postman_id`. Not sure why SDK is adding this field but it's not relevant in this case.