Fix enumUnknownDefaultCase in OpenAPI generator

[clementdenis]

Description

The recently added enumUnknownDefaultCase was not actually used. It now is:

public enum ChangeEnum {

    CHANGE("CHANGE"),
    
    KEEP_EXISTING("KEEP_EXISTING"),
    
    UNKNOWN_DEFAULT_OPEN_API("unknown_default_open_api");

   ...

}

Category

• Bugfix
• Enhancement
• New Feature
• Library Upgrade
• Configuration Change
• Versioning Change
• Unit or Integration Test(s)
• Documentation

Signoff

• I have submitted a CLA for this PR
• Each commit message explains what the commit does
• I have updated documentation to explain what my PR does
• My code is covered by tests if required
• I did not edit any automatically generated files

[arvindkrishnakumar-okta]

@clementdenis Thanks much for fixing this!

I'll close this in favor of mergeable PR #1002.

[royathan]

I wonder if this change led to the mis-casing of this method: addemailAddressesItem

[arvindkrishnakumar-okta]

@literallyjustroy Can you please elaborate?

[royathan]

Yes, sorry for the quick comment - I was in the middle of upgrading from 16.0.0 -> 17.00 and was looking around for a possible cause.

The 'addEmailAddressItem' method in the BouncesRemoveListObj class was renamed to 'addemailAddressItem'. That change in casing felt odd and perhaps unintentional. Could also have been related to the api generator upgrade as well.

Sorry I'm not super familiar with the project layout so wasn't able pinpoint the source of the change.

[arvindkrishnakumar-okta]

@literallyjustroy Thanks for the clarification!

Yes, it appears to be caused by the Open API Generator upgrade and was unintentional.