[BUG] Incorrect ENUM generation

[Noed]

Bug Report Checklist

• Have you provided a full/minimal spec to reproduce the issue?
• Have you validated the input using an OpenAPI validator (example)?
• Have you tested with the latest master to confirm the issue still exists?
• Have you searched for related issues/PRs?
• What's the actual output vs expected output?
• [Optional] Sponsorship to speed up the bug fix or feature request (example)

Description

ENUM is being generated with additional "_" character when there's a number on the ENUM name.

openapi-generator version

Issue started on 7.7.0, works fine on 7.7.6.

OpenAPI declaration file content or url

Example ENUM attribute in the YAML spec:

        myAttribute:
          description: this is a ENUM            
          type: string
          enum:
          - MOVE2STOCK
          - MOVE2SHELF
          - KEEP

Generation Details

Java 17, Gradle build.

Steps to reproduce

Add ENUM attribute to the spec that has numbers in the attribute name.
Generate java model using openapi generator 7.7.0.
Look into the source code generated, the ENUM attribute names will have an "_" after the number.

For example:

  public enum MyAttributeEnum {
    MOVE2_STOCK("MOVE2STOCK"),
    MOVE2_SHELF("MOVE2SHELF"),
    KEEP("KEEP"),

Related issues/PRs

Suggest a fix

[Trebuac]

Hello,
I got the same issue (different behaviour in my Java Enum generation between 7.6.0 and 7.7.0).

I suspect this commit to be the root cause : bfa26ea#diff-a98cba8ecadaf5a662edc508aa5857972339552ec6bd6e4216680c7c6070e643

which is linked to this request #4837

Sadly it seems that we can't change this behavior (some generator have the option to choose the 'enumPropertyNaming' -
'camelCase', 'PascalCase', 'snake_case', 'UPPERCASE', and 'original'), a feature request has been opened for Java/Spring : #18987

[wing328]

please refer to #18594 (comment) on how to fallback

[Maran23]

Is there an option to just use the enum as is? Without any futher modifications?

[AndresBena19]

Any idea when #19277 will be merged?

[magiusdarrigo]

@AndresBena19 +1000

[goldel777]

Can you help me understand if this when this will be fixed? I am still seeing underscores on the enums in 7.7.0 through 7.10.0. I've tried both this documented variations:

enumPropertyNaming=original,modelPropertyNaming=original
legacy

[goldel777]

Looks like this overrode me

Under configOptions:

additionalProperties : enumPropertyNaming=original,modelPropertyNaming=original</additionalProperties

enumPropertyNaming: legacy

[wing328]

Merged #20172 two weeks ago.

Please give it a try with the latest master or snapshot version.