The argument of the methodNameGenarator added in #663 is operationId, but it is actually the operationName by converted operationId to camelCase. If possible, I would like to use the raw operationId.
Is it possible to retain the operationId and use it in the methodNameGenerator?
Although, I have read this comment and understand that using operationName for consistency. https://github.com/hey-api/openapi-ts/pull/663#discussion_r1632639760
So I think it would be good to change the argument name to "operationName" and clearly state that it has been converted to camelCase. However, there is a concern that the name may be changed in the future for rational reasons.
Related issue: #535
OAS
openapi: 3.0.0
info:
title: Test
tags:
- name: Tag
components:
schemas:
Tag:
type: object
properties:
id:
type: string
required:
- id
paths:
/api/tag:
get:
operationId: Tag_get
parameters:
- name: test
in: path
description: description
required: true
schema:
type: string
example: example
responses:
"200":
content:
application/json:
schema:
$ref: "#/components/schemas/Tag"
tags:
- Tag
Description
The argument of the methodNameGenarator added in #663 is operationId, but it is actually the operationName by converted operationId to camelCase. If possible, I would like to use the raw operationId.
However, when reading the code, Operation does not have an operationId.
Is it possible to retain the operationId and use it in the methodNameGenerator?
Although, I have read this comment and understand that using operationName for consistency. https://github.com/hey-api/openapi-ts/pull/663#discussion_r1632639760 So I think it would be good to change the argument name to "operationName" and clearly state that it has been converted to camelCase. However, there is a concern that the name may be changed in the future for rational reasons.
Related issue: #535
OAS
Config
Stackblitz
https://stackblitz.com/edit/hey-api-example-sik3vs?file=openapi-ts.config.ts