Skip to content

v3.2.2

Compare
Choose a tag to compare
@axunonb axunonb released this 03 Aug 15:31
· 53 commits to main since this release
e98917a

What's Changed

Fix

  • PluralLocalizationFormatter does not treat a numeric string as valid argument (resolves #345, restore behavior of v3.1.0 and before) in #346

  • Bump version to v3.2.2

    Meaning: Smart.Format("{0:{}|is null or empty}", "1234"); will not implicitly invoke PluralLocalizationFormatter but instead ConditionalFormatter. So the result is "1234" as to be expected. A string argument to PluralLocalizationFormatter is never accepted, even if it could be converted to a number.

Chore

  • Update appveyor and github CI scripts
  • Update change log for v3.2.1 in #331
  • Update NuGet API Key in #335
  • Update link to pluralization rules we use as a reference in #338
  • Add unit test for DateOnly and TimeOnly types (NET6.0+) in #341

Full Changelog: v3.2.1...v3.2.2