incorrect nested query params serialization

[HeedjyCompany]

Hello,

I'm using the 12.0.2

When an endpoint has a query param containing a nested object like this :

- name: pageParams
          in: query
          required: false
          explode: true
          schema:
            $ref: "common.yaml#/components/schemas/PaginatedRequestParams"

    PaginatedRequestParams: 
      description:
        Page params to search the collection (this is an exploded object, so pass the inner properties directly)
      type: object
      properties:
        limit:
          description: Number of elements to retrieve
          type: integer
          default: 50
        cursor:
          description: Cursor from a previous search
          type: string
          format: base64
        returnCount:
          description: Set to 'true' to obtain the total count of the collection (use only when necessary, may be performance-costly)
          type: boolean
          default: false

The request query is serialized like this :

&pageParams=%5Bobject%20Object%5D

however the type seems ok :

 query?: {
...
                pageParams?: PaginatedRequestParams;
            },

Looking at the issue history, it seemed to be handled at a time but a reverted in this fix :
#228

[AshotN]

@HeedjyCompany were you able to resolve this?

[sbres]

I'm having the same issue this is annoying