You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@geniusescode Thanks for the report. I don't think we can do that actually:
Swagger doesn't support groups at all, but rather organizes endpoints by their path from the API root. That's what we're doing when exporting. But there's no support for custom groups, that's why they are ignored. (See Swagger 2.0 Spec)
Postman supports only one level of group (no nesting). Well, technically they support that in their new Postman format v2 but if we generate nested groups they are then ignored by the Postman user interface (bug or feature from them? we haven't checked tbh). The other issue with Postman format v2 is that we cannot export environment variables (not supported in v2), that's why we generate format v1. Regarding the groups, we could support group export with only the groups at the root, but we have chosen for now to put all requests under an "API-Flow imports" folder in Postman to make it clear to users.
I'll keep this issue open so we remember to check if we can support groups better when exporting to Postman.
JonathanMontane
changed the title
Export Paw groups to Postman/Swagger/RAML
Serializers - Paw - Export Paw groups to Postman/Swagger/RAML
Sep 26, 2016
when exporting the API's from POW to PostMan or swagger, groups get ignored,.
The text was updated successfully, but these errors were encountered: