transforming enum to delete the pathname at the enum name about openapi-typescript HOT 4 OPEN

At this time renaming isn’t supported in TypeScript because it could deviate from your schema; if two objects contained .gender how would the collision be fixed? Would you have Gender and Gender2? And more importantly, would it be clear when importing the type you were importing the correct one?

I’d recommend if you want to refer to an enum often, then move it to be its own top-level schema object in your OpenAPI spec itself. That way your generated types always match 1:1 to your schema, and you’ll never accidentally refer to one type thinking it’s another.

from openapi-typescript.

Every Enum that we defined has unique name. there are no way to create several kinds of enum called duplicated name.

is you mean that change the directory of the file that the enum defined to the top ?

from openapi-typescript.

Oh I had assumed that when you referenced #/components/schemas/com.aaaa.server.core.common.Gender, you were referencing multiple nested schema objects com → aaa → server → core → common → Gender, where each level was a property. In which case my suggestion would be to move it to #/components/schemas/Gender, and simply use $ref wherever it’s needed.

But if you are saying that is just a single schema object with periods in the title, then I think that’s the correct name? We want to match your schema 1:1 perfectly, without renames; but as those contain invalid characters we just do our best translating it into a valid JS identifier. But try and preserve the name as-authored so it’s easy-to-find and there’s no confusion.

from openapi-typescript.

Willing to look into it further if you can provide:

1. An example OpenAPI schema that generates an enum
2. What you expected it to generate

from openapi-typescript.