-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Using invariance culture when converting to string #4635
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
Using invariance culture when converting to string #4635
Conversation
@@ -145,7 +145,7 @@ public SweepableFloatParam(float min, float max, float stepSize = -1, int numSte | |||
|
|||
public override void SetUsingValueText(string valueText) | |||
{ | |||
RawValue = float.Parse(valueText, CultureInfo.InvariantCulture); | |||
RawValue = float.Parse(valueText); |
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 would instead push the culture invariant value into the sweepable parameter:
_valueText = _value.ToString("R"); |
Codecov Report
@@ Coverage Diff @@
## master #4635 +/- ##
==========================================
+ Coverage 75.63% 76.02% +0.39%
==========================================
Files 938 951 +13
Lines 168669 173945 +5276
Branches 18217 18885 +668
==========================================
+ Hits 127574 132247 +4673
- Misses 36065 36541 +476
- Partials 5030 5157 +127
|
Closing/reopening to restart CI tests. CI is failing w/ an odd Git checkout issue:
It sounds like it its trying to read from an non-existent commit hash. Perhaps restarting the CI will get the CI to read the current commit ID. |
Requesting a review from @tannergooding |
This will break It is also likely to break users who expect or depend on the invariant culture working (a culture which uses I would recommend just updating the |
Ah, nevermind. I see that the title no longer matches the change being provided. The actual change is updating |
For the required
It's only failing under I'll rerun the failing CI leg and hopefully the randomness falls in our favor. The previous Git issue was deterministic and restarting the CI seems to cause it to pick up the right commit ID. |
related Issue: