acacode / acacode/swagger-typescript-api

Params not created when only path variable are present

Open
#557 1 comment 1 reaction 0 assignees View on GitHub
Dominant language
TypeScript
Stars
4.1k
Forks
436
PR merge metrics
No merged PRs in 30d

Description

```
"/api1/{id}”: {
"get": {
"tags": [ ],
"summary": “blarblar1”,
"operationId": “api1”,
"parameters": [
{
"name": "id",
"in": "path",
"required": true,
"schema": {
"type": "integer",
"format": "int64"
}
}
],
"responses": {
~~~~
}
}
```
This is api with `id` parameters.
The parameter `id` is path variable.

```
"/api2/{id}": {
"get": {
"tags": [ ],
"summary": "blarblar2”,
"operationId": “api2”,
"parameters": [
{
"name": "id",
"in": "path",
"required": true,
"schema": {
"type": "integer",
"format": "int64"
}
},
{
"name": “date”,
"in": "query",
"required": true,
"schema": {
"type": "string"
}
}
],
"responses": {
~~~~
}
}
```
This is api with `id` and `date` parameters.
The parameter `id` is path variable, but parameter `date` is query parameter.

With Option `extractRequestParams: true`, Params type for api2 is created
```
export type TApi2Params = {
/** @format int64 */
id: number;
date: string;
};
```

But Params for api1 is not created
```
// I want this type to be created
export type TApi1Params = {
/** @format int64 */
id: number;
};
```

Is there a way to achieve this?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.