acacode / acacode/swagger-typescript-api

incorrect nested query params serialization

Ouverte
#464 4 commentaires 12 réactions 0 personnes assignées Voir sur GitHub
bug
Langage dominant
TypeScript
Étoiles
4.1k
Forks
436
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

Hello,

I'm using the 12.0.2

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

```yaml
- name: pageParams
in: query
required: false
explode: true
schema:
$ref: "common.yaml#/components/schemas/PaginatedRequestParams"
```
```yaml
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 :
```js
query?: {
...
pageParams?: PaginatedRequestParams;
},
```

Looking at the issue history, it seemed to be handled at a time but a reverted in this fix :
https://github.com/acacode/swagger-typescript-api/issues/228

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.