Ability to have custom functions called during conversion

[wabiloo]

During the conversion to Postman, we would like to be able to do some specific logic (eg. setting default values for parameters, adding tests, turning off optional parameters, etc.) for specific endpoints.

We typically mark those with custom attributes (eg. "x-bla" tags), but sometimes we do it just based on the endpoint name.

It would therefore be useful to have the ability for each openapi node being converted to be able to pass the node and context in a callback function, which can then apply transformations to the converted output

[joaonunogomes]

Hi!
Do you have any update about this ?
Thanks in advance

[abhijitkane]

@joaonunogomes Not yet, unfortunately. This module is included in the Postman application, so I don't think we'll be able to prioritise CLI-only features anytime soon. For the use-case described above, I'd recommend updating the OpenAPI file before importing, or using the options present in Postman import flow and this module to configure the import.

[thim81]

@wabiloo & @joaonunogomes

The openapi-to-postman package focusses on transforming a OpenAPI document to a Postman collection.

To make the transformation more dynamic, we have created a seperate package Portman that uses "openapi-to-postman" under the hood to transform OpenAPI document to a Postman collection, but while doing so, it offers options to generate automat tests, insert postman variables, prefill Params / Headers / Body values with environment variables, add pre-request scripts, ...

We initially created a PR (#225) on "openapi-to-postman", but it didnt feel right to mix functionality and that is why we created the Portman package, next to openapi-to-postman, leveraging openapi-to-postman but with automation, API testing & making Postman more dynamic in mind.