string parameters excluded with explode: true

[mhassan1]

Issue workflow progress

Progress of the issue based on the Contributor Workflow

• 1. The issue provides a reproduction available on Github, Stackblitz or CodeSandbox

Make sure to fork this template and run yarn generate in the terminal.

Please make sure Mesh package versions under package.json matches yours.

• 2. A failing test has been provided
• 3. A local solution has been provided
• 4. A pull request is pending review

---

Describe the bug

The following OpenAPI spec fails to include the expected explodedString query string parameter:

parameters:
  - name: explodedString
    in: query
    explode: true
    schema:
      type: string

The issue is related to the combination of explode: true and type: string.

To Reproduce
Steps to reproduce the behavior:

# .meshrc.yml
sources:
  - name: PetStore
    handler:
      openapi:
        baseUrl: https://petstore3.swagger.io/api/v3
        source: https://petstore3.swagger.io/api/v3/openapi.json

Execute this query:

{
  findPetsByStatus(status: available) {
    id
  }
}

See an error response:

{
  "data": {
    "findPetsByStatus": null
  },
  "errors": [
    {
      "message": "Unexpected response",
      "path": [
        "findPetsByStatus"
      ],
      "extensions": {
        "url": "https://petstore3.swagger.io/api/v3/pet/findByStatus?",
        "method": "GET",
        "responseText": "No status provided. Try again?",
        "error": {
          "name": "SyntaxError",
          "message": "Unexpected 'N'",
          "at": 1,
          "text": "No status provided. Try again?"
        }
      }
    }
  ]
}

Notice "url": "https://petstore3.swagger.io/api/v3/pet/findByStatus?" is missing the status=available query string parameter.

If I change explode: true in the PetStore spec to explode: false, the issue no longer reproduces.

Expected behavior

{
  "data": {
    "findPetsByStatus": [
      { "id": 1 }
    ]
  }
}

Environment:

• OS: MacOS
• @graphql-mesh/openapi: ^0.33.26
• NodeJS: 16.17.1

Additional context

• It seems like explode: true with strings doesn't make much sense, but it also seems like a case we should support
• I believe this is a regression introduced by Update openapi tests #4369