-
Notifications
You must be signed in to change notification settings - Fork 98
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
Custom culture #296
Custom culture #296
Conversation
Included an option for users to specify their preferred culture for the MSDN documentation links.
Thanks for the PR! From a quick look, it looks good. I'll review this and play around with it later this week. |
Hi, is there any news on the pull request? |
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.
Just some minor feedback. Thanks for this! Happy to merge this when the PR is updated and I'll get a new release spun out for this feature.
Apologies for taking a long time for getting this reviewed. I'm in the middle of wedding planning which leaves surprisingly little time for hacking on C# :)
return culture; | ||
} | ||
} | ||
} |
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.
Are we able to use CultureInfo.GetCultureInfo(String) instead of looping through all the cultures?
If guess that if the user specifies some invalid culture, GetCultureInfo
would throw -- I think it's fine to catch the exception and return some configuration error so the user knows their custom setting is not valid.
CSharpRepl.Tests/CommandLineTests.cs
Outdated
[Theory] | ||
[InlineData("--culture", "en-gb")] | ||
[InlineData("--culture", "en-GB")] | ||
[InlineData("--culture", "qwe", true)] |
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.
I think this should be an error, rather than silently ignoring the user's configuration
* CultureInfo.GetCultureInfo now throws CultureNotFoundException exception
@waf Congratulations!!! Сomments were resolved, now CultureNotFoundException is thrown |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #296 +/- ##
=======================================
+ Coverage 0.0% 77.5% +77.5%
=======================================
Files 83 83
Lines 5573 5584 +11
Branches 733 736 +3
=======================================
+ Hits 0 4328 +4328
+ Misses 5573 988 -4585
- Partials 0 268 +268
☔ View full report in Codecov by Sentry. |
Fix #293 #241
Add culture support for MSDN documentation links
Included an option for users to specify their preferred culture for the MSDN documentation links
Now we can define custom culture at config.rsp file