acacode / acacode/swagger-typescript-api

additionalProperties management problem in Swagger 2

Abierto
#343 3 comentarios 0 reacciones 1 asignado Reclamado por @js2me Ver en GitHub
bug
Lenguaje dominante
TypeScript
Estrellas
4.1k
Forks
436
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

In swagger 2, additionalProperties are very limited. They didn't support the true and {} values.
To replace this they define it like this

```
MyObject:
type: object
properties:
id:
type: string
additionalProperties:
type: object
```

It works only because in java like words String, Boolean and Numbers are Objects

in swagger 2, it must be transpiled in

```
export interface MyObject {
id?: string;
[key: string]: {}; // or [key: string]: any
}
```

but for now it is transpiled in
```
export interface MyObject {
id?: string;
}
```

result is the same If I try to transpile below code
```
MyObject:
type: object
properties:
id:
type: string
additionalProperties: {}
```

The only case the correctly works is
```
MyObject:
type: object
properties:
id:
type: string
additionalProperties: true
```

Swagger file is correctly converted with Swager.io typescript generators

Is it possible to fix it ?

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.