Handle free form query parameters

Describe the bug Given an OpenAPI 3 yaml file with a free-form query parameter, for example:

openapi: "3.0.0"
...
paths:
  /users:
    post:
      parameters:
        - name: userParameters
          in: query
          schema:
            type: object
            addtionalProperties:
              type: string
            style: form
...

when generating the postman spec file, then a query parameter (named “userParameters” from the example) is created into the output Postman spec file.

Steps to Reproduce

• Create an OpenAPI 3 yaml spec with a free-form query parameter
• Generate the Postman spec file
• Import the generated spec into Postman

Postman will insert the free-form query parameter as query parameter, and it will show the free-form query parameter name into the URL.

Expected behavior

• Postman should not show the free-form query parameter name into the URL.

App information (please complete the following information):

• Postman version: 7.1.1

Additional context A possible solution could be to remove the free-form query parameter from the generated postman spec file, for example updating the util.js getParametersForPathItem method as follows:

/**
   * Create parameters specific for a request
   * @param {*} localParams parameters array
   * @returns {Object} with three arrays of query, header and path as keys.
   * @no-unit-test
   */
  getParametersForPathItem: function(localParams) {
    var tempParam,
      params = {
        query: [],
        header: [],
        path: []
      };

    _.forEach(localParams, (param) => {
      tempParam = param;
      if ((tempParam.in === 'query') && (this.isFreeFormQueryParameter(param) == false)) {
        params.query.push(tempParam);
      }
      else if (tempParam.in === 'header') {
        params.header.push(tempParam);
      }
      else if (tempParam.in === 'path') {
        params.path.push(tempParam);
      }
    });

    return params;
  },

  /**
   * Check if the query parameter is a free-form query parameter
   * @param {*} parameter query parameter
   * @returns {Boolean} true if the parameter is a free-form query parameter.
   */
  isFreeFormQueryParameter: function(parameter) {
    return (parameter.schema !== undefined) && (parameter.schema.addtionalProperties !== undefined) && (parameter.schema.addtionalProperties instanceof Object) && (parameter.schema.style === 'form');
  },

[VShingala]

@marcoMobilab Yes, we have added support for serialization while conversion, this means all OAS defined styles are supported in params. For the definition provided by you mentioned behavior will be followed and For the given example try importing the below schema which should result in the mentioned behavior by you. (Make sure to use Example as value for Request parameter resolution option under Advanced Options)

openapi: "3.0.0"
info:
  title: User API
  version: 1.0.0
paths:
  /users:
    post:
      parameters:
        - name: firstName
          in: query
          description: The User first name
          required: true
          schema:
            type: string
            example: Henry
        - name: lastName
          in: query
          description: The User last name
          required: true
          schema:
            type: string
            example: Lee
        - name: userParameters
          in: query
          description: Additional custom User parameters
          schema:
            type: object
            addtionalProperties:
              type: string
            style: form
            example:
              age: 28
              weight: 78 

[marcoMobilab]

@VShingala with the second point I meant to say that the free-form query parameter could be a complex JSON object with arrays. But this is an optional feature, the main feature instead is to have the simple key-value free form parameters correctly handled. Take the following as an example:

Parameters of the POST request to the “/users” endpoint: firstName: Henry, lastName: Lee, userParameters: {“age”: “28”, “weight”: “78”}

POST request to the “/users” endpoint: POST /users?firstName=Henry&lastName=Lee&age=28&weight=78