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
This is mostly relevant if a path parameter is used in many paths. In my case it's like a hundred paths that use the parameter, which makes it too cumbersome to map manually. (workaround in the community post).
I think it makes sense to allow importing path parameters as variable at collection level instead of as path parameters as it is currently.
Especially if the path parameter is defined as a seperate component parameter, as it is in my spec. (spec, collection and environment available via the community post.)
Uh oh!
There was an error while loading. Please reload this page.
tldr: openapi path parameters are imported as ':var'. This prohibits mapping to an environment variable '{{var}} in bulk.
Issue described in this community post:
https://community.postman.com/t/importing-openapi3-with-path-variable/45427/3
This is mostly relevant if a path parameter is used in many paths. In my case it's like a hundred paths that use the parameter, which makes it too cumbersome to map manually. (workaround in the community post).
I think it makes sense to allow importing path parameters as variable at collection level instead of as path parameters as it is currently.
Especially if the path parameter is defined as a seperate component parameter, as it is in my spec. (spec, collection and environment available via the community post.)
This issue seems similar to: #643
The text was updated successfully, but these errors were encountered: