-
-
Notifications
You must be signed in to change notification settings - Fork 398
Fixes two edge cases with the mapping of double types #887
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
Fixes two edge cases with the mapping of double types #887
Conversation
Mirrors PR mini-software#886 on the maintenance branch
Summary of ChangesHello @michelebastione, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request refines the handling of Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
e2ae020
into
mini-software:v1.x-maintenance
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.
Code Review
This pull request addresses two edge cases in mapping double types. It now correctly uses the configured culture for parsing and throws an InvalidCastException on failure, which is more consistent with how other types are handled. The logic is sound. I've provided one suggestion to improve the readability of the new code.
| if (double.TryParse(Convert.ToString(itemValue, config.Culture), NumberStyles.Any, config.Culture, out var doubleValue)) | ||
| { | ||
| newValue = doubleValue; | ||
| } | ||
| else | ||
| { | ||
| var invariantString = Convert.ToString(itemValue, CultureInfo.InvariantCulture); | ||
| newValue = double.TryParse(invariantString, NumberStyles.Any, CultureInfo.InvariantCulture, out var value) | ||
| ? value | ||
| : throw new InvalidCastException($"Value \"{itemValue}\" cannot be cast to double"); | ||
| } |
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.
The logic here is correct, but the nested structure combined with a ternary expression using throw can be a bit dense and harder to read. Refactoring this to a more standard if-else structure would improve code clarity and maintainability without altering the functionality.
if (double.TryParse(Convert.ToString(itemValue, config.Culture), NumberStyles.Any, config.Culture, out var doubleValue))
{
newValue = doubleValue;
}
else
{
var invariantString = Convert.ToString(itemValue, CultureInfo.InvariantCulture);
if (double.TryParse(invariantString, NumberStyles.Any, CultureInfo.InvariantCulture, out var value))
{
newValue = value;
}
else
{
throw new InvalidCastException($"Value \"{itemValue}\" cannot be cast to double");
}
}
Mirrors PR #886 on the maintenance branch