Ignoring underscores in operationId results in duplicate functions

[evanhaldane]

Description

If your openapi spec has entries with operationIds like:

operationId: account___note_retrieve
...
operationId: account_note_retrieve

(which are auto-generated by drf-spectacular based on the paths)

then then both get mapped to accountNoteRetrieve (presumably because all underscores are ignored?)

This is using client-axios.

Reproducible example or configuration

npx @hey-api/openapi-ts -i 'schema.yml' -o src/schemas/mySchema -c @hey-api/client-axios

OpenAPI specification (optional)

/api/account/{blah}/{foo}-{bar}/note:
    get:
      operationId: account___note_retrieve
      parameters:
      - in: path
        name: blah
        schema:
          type: string
        required: true
      - in: path
        name: foo
        schema:
          type: string
        required: true
      - in: path
        name: bar
        schema:
          type: string
        required: true
/api/account/{blah}/note:
    get:
      operationId: account_note_retrieve
      parameters:
      - in: path
        name: blah
        schema:
          type: string
        required: true

System information (optional)

No response

[mrlubos]

@evanhaldane what would be the expected result beyond "it works"? You could choose to preserve the casing style which would work around this, but if you want to use certain casing, would appending a number work?

getAccountNoteRetrieve()
getAccountNoteRetrieve2()
getAccountNoteRetrieve3()
// ...

[evanhaldane]

@mrlubos that seems like a reasonable solution that should guarantee uniqueness while making it pretty clear they're different.

[mrlubos]

Let's do that then. Thanks for reporting!