Import Open API / Swagger 2.x Spec into Bruno

[helloanoop]

No description provided.

[dgmora]

Related to this one, something that I missed in insomnia and postman is that whenever my open api file changed, I had to re-import the collection. This kinda defeated the purpose, since the specification changes often. It would be great if that could be taken into consideration.

[olexandrvynnychenko]

Related to this one, something that I missed in insomnia and postman is that whenever my open api file changed, I had to re-import the collection. This kinda defeated the purpose, since the specification changes often. It would be great if that could be taken into consideration.

I would say it is not just something nice to consider. This little point would be a killer feature.

[michaeljauk]

Is there anyone currently working on this?

[esschul]

#578
Think something is happening here

[survivant]

we are working on an implementation. There is a PR here : #578
and I have my branch here : https://github.com/survivant/bruno/tree/feature/openapi-collection that contains some feature that the PR doesn't have.

But I'm not really a React dev, so it's not easy to implement it properly.

[dgmora]

Seems to be implemented, but for v3. Although for me it's failing because of #939

[hesparza]

This one is not working yet for swagger 2.x, is this being worked? I can help if required.

[mdefeche]

The body of most of my POST and PUT endpoints are empty (their are correctly detected in postman). Most PATCH endpoints have their body predefined with empty string as values

It would be nice to have the body set for POST and PUT endpoints and either have random values which match the field types or have the field type displayed as in postman

[survivant]

I opened a pr for that. Autogenerated body based on schema Le mer. 17 janv. 2024, 10 h 02, Martin ***@***.***> a écrit :

…

The body of most of my POST and PUT endpoints are empty (their are correctly detected in postman). Most PATCH endpoints have their body predefined with empty string as values It would be nice to have the body set for POST and PUT endpoints and either have random values which match the field types or have the field type displayed as in postman — Reply to this email directly, view it on GitHub <#81 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABO3B27J4FQO4UA5VYKCZLYO7RZVAVCNFSM6AAAAAAUKISJOKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJVHE4TKNJSGM> . You are receiving this because you commented.Message ID: ***@***.***>

[guynikan]

I opened a pr for that. Autogenerated body based on schema Le mer. 17 janv. 2024, 10 h 02, Martin @.> a écrit :
…
The body of most of my POST and PUT endpoints are empty (their are correctly detected in postman). Most PATCH endpoints have their body predefined with empty string as values It would be nice to have the body set for POST and PUT endpoints and either have random values which match the field types or have the field type displayed as in postman — Reply to this email directly, view it on GitHub <#81 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABO3B27J4FQO4UA5VYKCZLYO7RZVAVCNFSM6AAAAAAUKISJOKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJVHE4TKNJSGM . You are receiving this because you commented.Message ID: @.>

Where?

[Anutrix]

What's the status on it? Import from Insomnia still has missing/blank body.

[martin-braun]

I'm facing a public Swagger API and wish to try it out. I would greatly benefit from the ability to import this into Bruno by simply inserting the documentation URL somewhere. It's a bummer to learn that this is not part of the product, yet.

EDIT: So I checked the PR and it already landed. I can create a new collection and select "Import" > "OpenAPI v3" and pick my swagger.json that I downloaded. Awesome.

[darraghjones]

would be nice if the openapi spec could be imported from a URL

[vazome]

Related to this one, something that I missed in insomnia and postman is that whenever my open api file changed, I had to re-import the collection. This kinda defeated the purpose, since the specification changes often. It would be great if that could be taken into consideration.

Essentially, there are two missing features:

1. Continuous collection sync with OpenAPI spec, not just import
2. Prefill body/query based on the values that were specified in "examples" Import examples when importing OpenAPI #2320

We can now import OpenAPI both via URL and file, but if that spec changes (especially during development) you need to redo collection import and have global environment defined (I didn't know there were global environments).