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
I want to automate the update of our Postman collection from our OAS file during the pipeline. However, every time that I run the script, the example data (id, texts, etc) are recreated, and this would pollute all the following PRs.
Is there a way to avoid the example data to be recreated? Maybe through a seed?
The text was updated successfully, but these errors were encountered:
As a workaround, you can explicitly specify every example value in the OpenAPI spec. The OpenApi2Postman process fills in missing or invalid values with random values, but respects ones you've specified. It can be a lot of work for a large API.
It would be nice if the auto-generation was configurable. Even if it was only to be able to specifying the random seed. Making it deterministic would prevent issues with things like PRs. At the moment, if you miss a single string field example, it will spew fragments of latin.
I want to automate the update of our Postman collection from our OAS file during the pipeline. However, every time that I run the script, the example data (id, texts, etc) are recreated, and this would pollute all the following PRs.
Is there a way to avoid the example data to be recreated? Maybe through a seed?
The text was updated successfully, but these errors were encountered: