Two endpoints with same name conflicting data type

[danilofuchs]

Description

We have two endpoints with the same name:
changeUserPassword (user facing) and changeUserPassword (management only, different payload), the generated API only has one ChangeUserPasswordData without an id parameter:

export type ChangeUserPasswordData = {
  requestBody: {
    current_password: string;
    new_password: string;
  };
};

#538 should have fixed this

@hey-api/openapi-ts 0.43.2

OpenAPI specification (optional)

The management endpoint has an id parameter

    "/users/change-password": {
      "post": {
        "operationId": "changeUserPassword",
        "tags": [
          "App"
        ],
        "description": "Changes a user's password.",
        "requestBody": {
          "content": {
            "application/json": {
              "schema": {
                "type": "object",
                "properties": {
                  "current_password": {
                    "type": "string"
                  },
                  "new_password": {
                    "type": "string"
                  }
                },
                "required": [
                  "current_password",
                  "new_password"
                ]
              }
            }
          },
          "required": true
        },
        "responses": {
          "200": {
            "description": "",
            "content": {
              "application/json": {
                "schema": {
                  "type": "object",
                  "properties": {}
                }
              }
            }
          }
        },
        "deprecated": false,
        "parameters": []
      }
    },
    
    "/management/users/{id}/change-password": {
      "post": {
        "operationId": "changeUserPassword",
        "tags": [
          "Management App Users"
        ],
        "description": "Change user password",
        "requestBody": {
          "content": {
            "application/json": {
              "schema": {
                "type": "object",
                "properties": {
                  "current_password": {
                    "type": "string"
                  },
                  "new_password": {
                    "type": "string"
                  }
                },
                "required": [
                  "current_password",
                  "new_password"
                ]
              }
            }
          },
          "required": true
        },
        "responses": {
          "200": {
            "description": "",
            "content": {
              "application/json": {
                "schema": {
                  "type": "object",
                  "properties": {}
                }
              }
            }
          }
        },
        "deprecated": false,
        "parameters": [
          {
            "name": "id",
            "in": "path",
            "required": true,
            "schema": {
              "type": "string",
              "format": "uuid"
            }
          }
        ]
      }
    },

Configuration

openapi-ts -i https://test.com/openapi.json -o src/server/test-api --name TestApi --client fetch --format prettier

System information (optional)

No response

[mrlubos]

@danilofuchs this is because of the duplicate operationId in your OpenAPI specification. From Swagger docs

operationId is an optional unique string used to identify an operation. If provided, these IDs must be unique among all operations described in your API

Assuming you have control over your spec, this should be fixed on the API side