[C#] allow customization of generated enum suffixes

[scottdallamura]

allows customization of enum suffixes for C#
addresses #4275

{
    "apiPackage": "RestApi.Controllers",
    "modelPackage": "RestApi.Models",
    "packageName": "RestApi",
    "enumNameSuffix": "aaa",
    "enumValueNameSuffix": "bbb"
}

generates stuff like (not that i would ever want 'aaa' or 'bbb' suffixes, but it's a fine example...)

        /// <summary>
        /// Gets or Sets Status
        /// </summary>
        [TypeConverter(typeof(CustomEnumConverter<Statusaaa>))]
        [JsonConverter(typeof(Newtonsoft.Json.Converters.StringEnumConverter))]
        public enum Statusaaa
        {
            
            /// <summary>
            /// Enum Activebbb for Active
            /// </summary>
            [EnumMember(Value = "Active")]
            Activebbb = 1,
            
            /// <summary>
            /// Enum Disabledbbb for Disabled
            /// </summary>
            [EnumMember(Value = "Disabled")]
            Disabledbbb = 2
        }

PR checklist

• Read the contribution guidelines.
• If contributing template-only or documentation-only changes which will change sample output, build the project before.
• Run the shell script(s) under ./bin/ (or Windows batch scripts under.\bin\windows) to update Petstore samples related to your fix. This is important, as CI jobs will verify all generator outputs of your HEAD commit, and these must match the expectations made by your contribution. You only need to run ./bin/{LANG}-petstore.sh, ./bin/openapi3/{LANG}-petstore.sh if updating the code or mustache templates for a language ({LANG}) (e.g. php, ruby, python, etc).
• File the PR against the correct branch: master, 4.1.x, 5.0.x. Default: master.
• Copy the technical committee to review the pull request if your PR is targeting a particular programming language.

[auto-labeler]

👍 Thanks for opening this issue!
🏷 I have applied any labels matching special text in your issue.

The team will review the labels and make any necessary changes.

[scottdallamura]

copying the technical committee ...
@mandrean @jimschubert @frankyjuang

[scottdallamura]

so i think i figured out how to run the scripts, and indeed a bunch of files were generated. i expected the aspnetcore one (and i've committed the updated version) but it's unclear to me why so many samples for other languages were generated. i'm trying it without my changes now.

[scottdallamura]

looks ready to go? let's do it

[wing328]

Thanks for the PR but your commit (as shown in the Commits tab) is not linked to your Github account, which means this PR won't count as your contribution in https://github.com/OpenAPITools/openapi-generator/graphs/contributors.

Let me know if you need help fixing it.

Ref: https://github.com/OpenAPITools/openapi-generator/wiki/FAQ#how-can-i-update-commits-that-are-not-linked-to-my-github-account

[scottdallamura]

oops. fixed it!

[jimschubert]

What is the use case for this? Why wouldn't someone just put the expected value in the enum text field in the specification document?

[scottdallamura]

The behavior before my change is to append Enum to both the name of the enum type and each value. So you end up with

enum MyEnum {
  Value1Enum,
  Value2Enum
}

I didn't want to break the existing default behavior, so I made that suffix customizable too.

If you have suggestions I'd be happy to change it :)

[jimschubert]

Sorry for the delay in response. The holidays were pretty hectic for me.

I think we'll want to call the value one enumValueSuffix. I'll do that in a separate commit.