pr-support-postman-variables-query

[thim81]

Fix for unwanted encoding of Postman variables in query string, but keep support for "space".

In #93, we introduced URI.encodeReserved(feature.address.query()) to leverage encoding of query string to handle spaces/+ properly.

The [URI.encodeReserved()](http://medialize.github.io/URI.js/docs.html#static-encodeReserved) handles the special properties, but also encode the {{}} syntax for Postman variables, which is not desired.

In this PR, I made the proposal to remove URI.encodeReserved() but still keep the support of "space" encoding.

In attachment you can find the correct result for a postman collection with 2 query string with {{}}, + and space.

[thim81]

script.js.txt
TestCollection.postman_collection.json.txt

[thim81]

Linked to #106 and #104

[thim81]

For those that run into the issue of the encoding, I have provided a forked NPM package version that contains a fix for the issue:

Replace in your packages.json:

"dependencies": {
    "postman-to-k6": "^1.5.0"
  }

to

"dependencies": {
    "@apideck/postman-to-k6": "^1.7.0"
  }

This is a forked NPM package, to facilitate other users. The current maintainers are quite overloaded by the acquisition of K6 by Grafana. By forking the repo & package, users can keep using new PR's & (security) fixes. At a later stage the changes can potentially be merged back in the original postman-to-k6 repo.

The changelog contains the differences between the original package & the forked version.