ContributionsMost RecentMost LikesSolutionsRe: Mass import Postman collection/requests into Swagger Explore API/operation Weβve released 0.8.0 of ππ π½πΉπΌπΏπ².ππΉπΆ which now has support for nested Postman Collections as part of itβs import. Root level requests are now added to an Explore API folder with same name as Explore Space (e.g. Postman collection 'foo' with requests will create Explore Space 'foo' with API folder 'foo' which will contain the request connections). Nested folders within a collection, will have a name format of Parent - Child (e.g. foo/bar will create API folder called foo - bar, foo/bar/baz will create API folder called foo - bar - baz) Also, in case you missed it, we also support an`ππππππ-ππππ-ππππ` feature allowing you to explore the API calls representing consumer expectations within a Pact contract. Install via Nuget: https://www.nuget.org/packages/Explore.Cli Standalone binaries: https://github.com/SmartBear-DevRel/explore-cli/releases/tag/0.8.0 Community Feedback Request: How are you using Swagger Editor and what's your experience? π Hi There. Are you a Swagger Editor user? Get your chance to shape the future of API Editors, by answering a few questions about your usage experience, and help share ways to improve the product. πΈπΈ To show our appreciation for your time, weβre offering up to 100 swag points for completing the short survey. Take the survey: https://www.surveymonkey.com/r/Swagger-Editor-Usage-Survey Re: Need Help Escalating PR Hi emead The PR has been merged. Cheers, Frank Explore What's New - Import Insomnia Collections and Explore.CLI Standalone binaries In this episode πΊ, we walk through the new `import-insomnia-collection` command of the Explore.CLI. Now you can easily import collections from Insomnia directly into SwaggerHub Explore as spaces. Additionally, Explore.CLI now comes with standalone binary options meaning you do not need to have .NET installed to start leveraging the CLI. Check out the short video covering the features: https://www.youtube.com/watch?v=HJIs7L6XTls Download the CLI to get Exploring! https://www.nuget.org/packages/Explore.Cli https://github.com/SmartBear-DevRel/explore-cli/releases Re: Mass import Postman collection/requests into Swagger Explore API/operation FYI - this item is being tracked under the following GitHub issue: https://github.com/SmartBear-DevRel/explore-cli/issues/36 Re: Consistent HTTP 500 Error When I Click Export API To SwaggerHUB chewbika The Postman collections issue you linked above is a different issue that was just related to the CLI. However, the Expore API to SwaggerHub issue that was related to this original post appears to have been resolved. FYI zx11ninja Re: Mass import Postman collection/requests into Swagger Explore API/operation Hi chewbika What you describe is the current behaviour. If you could create an GitHub issue, I'll see about adding the ability to group requests under a single connection when within the same folder level. https://github.com/SmartBear-DevRel/explore-cli/issues Re: Consistent HTTP 500 Error When I Click Export API To SwaggerHUB Thanks chewbika There is a ticket raised with the engineering team regarding this issue. Once a fix is available, I'll comment back here. Re: Swagger not rendering multiple schemas Hi mtiwari176 Do you need to use discriminator here? If the goal is to just show examples of the different schemas to the consumer, then you could have: responses: '200': description: search results matching criteria content: application/json: schema: type: array items: oneOf: - $ref: '#/components/schemas/Schema1' - $ref: '#/components/schemas/Schema2' examples: Schema1: value: subject: foo Schema2: value: subject: bar This would then render as follows in SwaggerUI and allow a consumer to select the appropriate example and see the schemas: Re: Consistent HTTP 500 Error When I Click Export API To SwaggerHUB Hi chewbika, The `export-spaces` file is not expected to be imported into SwaggerHub. This is only relevant within the context of the Explore tool. If you can share your space with me I'll take a look to see why the import to SwaggerHub is not working. Options: Via the GUI of Explore, navigate to `spaces`, click on the 3 dots of the space you want to expore, click `share snapshot`. You can send me the link. Alternatively, past in the full export-spaces file (redacting any auth or server info) here.