An `Enum`, unknown at compile time, can no longer be used with `EnumHumanizeExtensions.Humanize`

[imm-mcc]

First off, thanks for the great package! It's incredibly useful.

I updated to v3 of Humanizer and I was no longer able to compile, with several of the following errors:

The type 'Enum' must be a non-nullable value type in order to use it as parameter 'T' in the generic type or method 'EnumHumanizeExtensions.Humanize<T>(T, LetterCasing)'

After some investigation, it looks like commit 7e7e960 changed the signature of the extension method from:

public static string Humanize(this Enum input, LetterCasing casing)

to:

public static string Humanize<T>(this T input, LetterCasing casing) where T : struct, Enum

thereby requiring the concrete type of the Enum to be known at compile time.

Is this an intentional change? If so, are there any workarounds that you'd suggest?

[BravermanMillimanCRS]

Possibly related: After updating an ASP.NET Core app to Humanize 3.0.1, a dependency compiled with 2.14.1 threw this exception:
System.MissingMethodException: 'Method not found: 'System.String Humanizer.EnumHumanizeExtensions.Humanize(System.Enum)'.'

Both the package and the app are running .NET 10.

[RuslanLatsina]

Same issue

[Winter979]

have the same issue, temp resolved it by just using reflection but hope that is permanent.

[sanny82]

same issue. Seems strange to break something so basic

[xkz1994]

+1

    public object Convert(object? value, Type targetType, object? parameter, CultureInfo culture)
    {
        return value is Enum enumValue ? enumValue.Humanize() : ThrowHelper.ThrowNotSupportedException<object>(nameof(value));
    }