Update Humanizer.Core to 3.x

[drewburlingame]

Description

Update Humanizer.Core from version 2.14.1 to 3.x.

Current Version

• Humanizer.Core: 2.14.1

Target Version

• Humanizer.Core: 3.x (latest stable)

Why Update?

• Security updates
• New features and improvements
• Keep dependencies current

Considerations

⚠️ Version 3.x contains breaking changes - requires careful testing:

1. Test Areas:

   • CommandDotNet.NameCasing functionality
   • All name transformation features
   • Ensure backward compatibility for library users

2. Migration Steps:

   • Review Humanizer.Core 3.x changelog for breaking changes
   • Update code if necessary
   • Run full test suite
   • Test example applications
   • Verify no API changes affect library consumers

3. Used By:

   • CommandDotNet.NameCasing project (~57 lines)

Tasks

• Review Humanizer.Core 3.x changelog
• Update package version in Directory.Packages.props
• Update any affected code
• Run full test suite (ensure all 950+ tests pass)
• Test CommandDotNet.NameCasing examples
• Update release notes if needed

Resources

• Humanizer GitHub
• Humanizer NuGet

Labels

enhancement, dependencies

[drewburlingame]

Investigation Results: Update Blocked

I investigated updating Humanizer.Core from 2.14.1 to 3.x and found that we're currently blocked from upgrading.

Blocker: Analyzer Compatibility Issue

The latest version 3.0.0-rc.29 (still in Release Candidate) includes a Roslyn analyzer that targets .NET 10.0, but CommandDotNet targets .NET 8.0 and 9.0.

Build Error:

CSC : error CS8032: An instance of analyzer Humanizer.Analyzers.NamespaceMigrationAnalyzer cannot be created from 
/Users/drew/.nuget/packages/humanizer.core/3.0.0-rc.29/analyzers/dotnet/net10.0/cs/Humanizer.Analyzers.dll : 
Could not load file or assembly 'System.Collections.Immutable, Version=10.0.0.0, Culture=neutral, 
PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.

Attempted Solutions (All Failed)

1. ❌ <ExcludeAssets>analyzers</ExcludeAssets> in Directory.Packages.props
2. ❌ <PrivateAssets>analyzers</PrivateAssets> in project files
3. ❌ <Analyzer Remove="..." /> in Directory.Build.props and project files

The analyzer is automatically loaded by MSBuild from the NuGet package and requires .NET 10 dependencies that don't exist in .NET 8/9 environments.

Recommendation

Wait for one of the following:

1. Humanizer 3.0.0 stable release that either:

   • Includes multi-targeted analyzers (net8.0, net9.0, net10.0)
   • Fixes the analyzer compatibility issue
   • Removes the problematic analyzer

2. CommandDotNet upgrades to .NET 10 (future release)

Impact Assessment

Low Impact - Humanizer.Core is only used in CommandDotNet.NameCasing (~36 lines) for simple string case transformations:

• Camelize()
• Dehumanize()
• Kebaberize()
• Underscore()

Next Steps

• Monitor Humanizer releases for stable 3.0.0
• Revisit after stable release or .NET 10 upgrade
• This issue should remain open as a reminder to upgrade when feasible