Enum option cannot generate enums if values are not valid property names

[jekh]

Description

When there are multiple keys that cannot be represented as properties, the generated enum converts them all to _, which makes it impossible to use those values in the enum.

Name	Version
openapi-typescript	7.0.0
Node.js	20
OS + version	Linux

Reproduction

A decent example is the Intercom OpenAPI spec: https://github.com/intercom/Intercom-OpenAPI/blob/main/descriptions/2.11/api.intercom.io.yaml

When generating types using:

openapi-typescript ./api.intercom.io.yaml --enum -o ./intercom.d.ts

It results in an enum that looks like this:

export enum Single_filter_search_requestOperator {
    _ = "=",
    _ = "!=",
    IN = "IN",
    NIN = "NIN",
    _ = "<",
    _ = ">",
    _ = "~",
    _ = "!~",
    _ = "^",
    $ = "$"
}

Expected result

Quoted key names if they are not valid javascript properties. For example, something like this:

export enum Single_filter_search_requestOperator {
    "=" = "=",
    "!=" = "!=",
    IN = "IN",
    NIN = "NIN",
    "<" = "<",
    ">" = ">",
    "~" = "~",
    "!~" = "!~",
    "^" = "^",
    $ = "$"
}

Checklist

• My OpenAPI schema passes the Redocly validator (npx @redocly/cli@latest lint)
• I’m willing to open a PR (see CONTRIBUTING.md)

[drwpow]

Great, reproducible example, thank you! This PR would be a great simple fix if someone is able to provide one.

[dsinghvi]

@jekh The Intercom folks have released a new alpha version of their SDK (intercom/intercom-node#416). Would you be interested in giving that a swing?

[htunnicliff]

@drwpow I think this issue was fixed in #1761, but I'm not positive. Any chance you could take a peek and confirm?

[drwpow]

Yes I believe so! But if anyone notices any additional issues, please let us know.