Closed edjanx closed 7 years ago
Thanks for bringing this to our notice. We shall keep you updated on this thread when we start taking this up.
Thanks @SamvelRaja - I also just upgraded to RAML 1.0 because this is now the supported version e.g. in API Workbench; RAML2HTML... so it just makes sense for Postman to use it.
Closing as a duplicate. We will look into this soon after introducing multi-level folders.
Which issue is duplicating this one?
I also would like to see RAML 1.0 supported especially in the "Tests" tab in postman with response code validation, schema validation, etc. i.e.: basic checks extracted from the definition of the API in RAML v1.0 with types
I couldn't agree more it would be so useful to be able import the RAML available on our MuleSoft's Exchange API portals, which have fully documented data type descriptions and examples fully defined. Not it's an extra step to manually create a Postman collection after the RAML is defined, which we don't have the Dev Cycles for.
Ed Jankauskas
On Dec 20, 2017 5:12 AM, "Sébastien" notifications@github.com wrote:
Which issue is duplicating this one?
I also would like to see RAML 1.0 supported especially in the "Tests" tab in postman with response code validation, schema validation, etc. i.e.: basic checks extracted from the definition of the API in RAML v1.0 with types
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/postmanlabs/postman-app-support/issues/3057#issuecomment-353022209, or mute the thread https://github.com/notifications/unsubscribe-auth/ANUYi4zQZ7YTI9AMYXonbYK9oC-H4p4hks5tCN2QgaJpZM4Ni72Q .
@a85 what is this a duplicate of? As others have mentioned, this would be very valuable for MuleSoft developers (such as me). Thank you!
Although RAML 0.8 import is currently supported, our company has fully migrated to RAML 1.0 to take advantage of it's powerful capabilities.
Generating a Collection from RAML 1.0 will save our Dev team valuable time, as they must manually create these collections now. The import would eliminate rework and allow development activity to replace the current manual documentation effort.