-
Notifications
You must be signed in to change notification settings - Fork 965
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pluralizer bug #1030
Comments
Looks like all 7 words here ignore casing of original word: https://github.com/Humanizr/Humanizer/blame/master/src/Humanizer/Inflections/Vocabularies.cs#L97 |
I'm new to open source but I would like to fix this. |
Not fixed yet? Seems like an easy one to fix. Not sure why using extra stuff is becoming default. Remember this new EF is going to be simple and basic, otherwise people will run away. Hard enough getting new devs to use it after the old EF experience. I get the reason for plurals but does it have to be so evasive? |
@clairernovotny Great, when is a new release planned with the fix? |
Soon as I can narrow down the cause of the test failures here when running on .NET 5: |
That's.... Interesting! |
@cgountanis This fix is now included in the latest build of EF Core Power Tools |
@clairernovotny Thanks, I noticed! |
Thanks Erik, looks like they fixed it at some point in the next Sprint or release as well. Not trying to ignore the power tools but I really don't want to use any third-party stuff for obvious reasons. |
Bug:
Pluralize or Singularize
Training
Expected:
Training
Actual:
training
(lower case t)See dotnet/efcore#24040
The text was updated successfully, but these errors were encountered: