You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are many enum name generation options in the current ts-swagger generator. They work wonders, however, there are many cases in which users may want to retain the original enum name as closely as possible. Of course, in the OAS there can be invalid characters, but many enums follow predictable casing such as UPPER_SNAKE or even lower_snake, among others. The idea would be to strip out invalid characters and preserve the rest of the name. This should be similar to the existing options.
This would allow users to continue to use their originally formatted enum names, even if it's in a cursed casing like SpOnGeBoBcAsE and then use either as const or enum or const enum.
What is the problem this feature would solve?
There are many enum name generation options in the current ts-swagger generator. They work wonders, however, there are many cases in which users may want to retain the original enum name as closely as possible. Of course, in the OAS there can be invalid characters, but many enums follow predictable casing such as
UPPER_SNAKE
or evenlower_snake
, among others. The idea would be to strip out invalid characters and preserve the rest of the name. This should be similar to the existing options.This would allow users to continue to use their originally formatted enum names, even if it's in a cursed casing like
SpOnGeBoBcAsE
and then use eitheras const
orenum
orconst enum
.For example
External documents/projects?
No response
What is the feature you are proposing to solve the problem?
No response
What alternatives have you considered?
No response
The text was updated successfully, but these errors were encountered: