-
Notifications
You must be signed in to change notification settings - Fork 734
Expand Locale parser to support three-character language codes #6124
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
Expand Locale parser to support three-character language codes #6124
Conversation
7c3e4a0 to
3cf400c
Compare
…three-letter locales
3cf400c to
d0a4d36
Compare
src/NuGet.Core/NuGet.Packaging/ContentModel/ManagedCodeConventions.cs
Outdated
Show resolved
Hide resolved
jeffkl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fix!
|
@baronfel What .NET SDK version did this make it into? |
|
9.0.200+ for sure, perhaps 9.0.100 but I'm not certain given the backport bar... |
|
Issue says 6.13, so that's 9.0.200 https://learn.microsoft.com/en-us/nuget/release-notes/nuget-6.13 |
|
Fantastic, thank you. I've been preparing to release Humanizer 3.0 -- an RC is currently live now -- and I added the fil locale back into the default metapackage. I'll give it a go on SDK 8 and see if/how it breaks 😅. What is the current story with the .NET Framework version of MSBuild w.r.t. NuGet client versions? I'm trying to understand the potential impact of this as I do not want to suddenly break people! :) |
|
17.13 and newer should have this fix. |
Bug
Fixes: NuGet/Home#12253
Description
Per NuGet/Home#12253 (comment), I found that all cultures known to .NET on my Windows and Linux hosts used 2 or 3-character language codes, so I expanded the heuristic in the
Locale_Parserto this to enable handling of resources for these locales in .NET packages. I also added comments explaining why these decisions were made and a note about future fully-correct implementations if those become required.PR Checklist