Support of path variables?

[alexibz]

I've tried to generate a postman collection from an open api v3 spec, and the Path variables show up as <string>, is there a way to have them as a postman variable instead, i.e. {{appId}}?

[abhijitkane]

@alexibz The <string> bit is useful in documentation generated from the collection (https://learning.postman.com/docs/postman/api-documentation/documenting-your-api/). We could expose an option where the user can choose what the generation should look like.

Is appId a parameter that will have the same value across multiple requests?

[alexibz]

Yes, I've learned the correct term would be placeholder. It would be very helpful if a user can generate placeholders for some variables, similar to how right now it is for {{baseUrl}}.

[thim81]

@alexibz

I have faced the same problem, so I create a PR #231 to solve this by using the configuration options "example/schema".

If you have remarks or issues let me know.

OpenApi screenshot:

Postman screenshot:

[thim81]

@alexibz

In the 1.2.0 release, the reworked this properly and path variables are now supported properly.

[VShingala]

@thim81 @alexibz Just to clarify the fix is now available in this module itself. And it will be available in Postman Native App in upcoming release.

[abhijitkane]

The option to choose example/schema-based generation is now available in Postman.