-
Notifications
You must be signed in to change notification settings - Fork 15.6k
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
Fix 32-bit floating point JSON parsing of maximal values for C# #10514
Conversation
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.
LGTM
[TestCase("3.4028236e38", typeof(InvalidProtocolBufferException))] | ||
[TestCase("-3.4028236e38", typeof(InvalidProtocolBufferException))] |
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.
super tiny nit (and just so that is clear at first sight that the string format is not the problem, use the same format in the valid and invalid tests):
[TestCase("3.4028236e38", typeof(InvalidProtocolBufferException))] | |
[TestCase("-3.4028236e38", typeof(InvalidProtocolBufferException))] | |
[TestCase("3.4028236e+38", typeof(InvalidProtocolBufferException))] | |
[TestCase("-3.4028236e+38", typeof(InvalidProtocolBufferException))] |
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.
Hmm... both formats should work. I'll update the tests to have both "with +" and without.
5decb39
to
77bdd5e
Compare
77bdd5e
to
3874b22
Compare
3874b22
to
fc1dbc6
Compare
Fixes #10509.