-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Use json for writing floats as strings #4934
Conversation
adb62e2
to
25562d2
Compare
Codecov Report
@@ Coverage Diff @@
## main #4934 +/- ##
==========================================
- Coverage 91.06% 91.04% -0.03%
==========================================
Files 180 180
Lines 10680 10700 +20
==========================================
+ Hits 9726 9742 +16
- Misses 737 740 +3
- Partials 217 218 +1
Continue to review full report at Codecov.
|
7b87ae9
to
7e5de54
Compare
c7d01d5
to
fc5ac27
Compare
This is ready for review |
fc5ac27
to
d488758
Compare
@dashpole maybe rebase to re-trigger checks? |
0953993
to
f5746c2
Compare
pushed again |
@dashpole not sure what happens,.... maybe open a new PR from a cloned branch? |
it woke up! |
f5746c2
to
d35ed29
Compare
rebased |
* use json for writing floats as strings * avoid using reflection for floats * extra unit test * fix rebase Co-authored-by: Bogdan Drutu <[email protected]>
Description:
This is the change that would be required by open-telemetry/opentelemetry-specification#2343. It changes how small floats are represented by using the json marshaller. The test would fail with the current implementation, as it returns ".000000009" instead of "9e-9".