Ship Humanizer 2.1

[clairernovotny]

Issue to track shipping Humanizer 2.1.

In addition to the bug fixes since 2.0.1, this version will support netstandard. As such, it will also require a minimum NuGet version of 2.12 to install correctly.

@hazzik @aloisdg @mexx Please add items to this list that need to be complete before we ship.

• Merge in netstandard branch
• Ensure assembly versions are updated Keep assembly information/version up-to-date. #535
• Modified PascalCaseWordPartsRegex to accept more "word characters" Modified PascalCaseWordPartsRegex to accept more "word characters" #564
• Handling of null, blank and untrimmed collection items Handling of null, blank and untrimmed collection items #566
  • Resolve the issue with overloads instead of optional arguments

[aloisdg]

I am working to port Numbro to Humanizer. The related issue is #558. The PR should be ready as soon as #568 is fixed and I achieve to build 😄

Also:

• I want to support Esperanto DateTime, but the code doesn't exist yet.
• The support for the french "avant-hier/" and "après-demain" will be postpone.
• There are old codes inside NumberToWords. I would like to move it C#6 (string interpolation, etc.). It could be postpone since it would be plain refactoring.

One item should be ready:

• Add esperanto support to NumberToWords Add Esperanto support for NumberToWords #558 (PR: Add Esperanto support to NumberToWords. Fixes #558 #569)

[hazzik]

I would like to nominate following: (moved to the first message)

[aloisdg]

@onovotny Can you update the milestone in each issue/PR?

[aloisdg]

I would like to propose #518 by @i3arnon (PR: #519)

[hazzik]

What if we just let the GitVersion decide the next version number? This will allow us to just ship without looking into the details and version holds.

[clairernovotny]

@hazzik GitVersion is just a tool...it does whatever we want it to. In general, here's a good take on it:
https://docs.microsoft.com/en-us/dotnet/articles/core/versions/index#semantic-versioning

By that logic, it feels like a 2.1 for this release.

[hazzik]

I know that this shall be a 2.1. But what I'm trying to say: we do +semver: hints on commits, and just release whatever version is calculated by GitVersion.

[hazzik]

Hey-hey. I've merged #566. 🚢 the 2.1.

[clairernovotny]

I generally tag the final version and that will automatically set it in GitVersion

[clairernovotny]

Note that Humanizer is completely broken on dotnet CLI due to this: https://github.com/dotnet/cli/issues/3396. It won't install/restore succesfully. Only the english locale will work, Humanizer.Core.

Try it today with the MyGet/CI feed; you cannot restore it into an xproj. It works just fine in a csproj that uses netstandard.

[clairernovotny]

I may have a workaround for this that I'm testing -- a Humanizer.xproj package that has all of the files and resources in the same package (like Humanizer 1.x did before the split). This should work but I'll verify. I'll nuke the package once the cli bug is fixed or things transition to msbuild in the fall.

[clairernovotny]

Confirmed, the Humanizer.xproj works. Now just need docs and release notes and we're good to go.

[clairernovotny]

2.1 has been pushed to NuGet. Should be visible soon.