When using postman variables as path parameters the tool correctly interprets these as parameters which can be changed by end users of the swagger doc.
If we use the replace variables flag then they values from them are substituted as expected, but then they are no longer recognised as a parameter.
A nicer solution is to add a flag where we can instead of doing variable replacement set the postman variable values as parameter examples... doing so they become the default value in the doc but can still be overridden by the end user.
Since version 1.17.0 the correct way to define path variables is using the postman way, see #130 for more info, this is totally compatible with variable replace.
When using postman variables as path parameters the tool correctly interprets these as parameters which can be changed by end users of the swagger doc.
If we use the replace variables flag then they values from them are substituted as expected, but then they are no longer recognised as a parameter.
A nicer solution is to add a flag where we can instead of doing variable replacement set the postman variable values as parameter examples... doing so they become the default value in the doc but can still be overridden by the end user.