Skip to content
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

ensure empty values are not deserialized #436

Merged
merged 1 commit into from
Jun 8, 2024

Conversation

biojppm
Copy link
Owner

@biojppm biojppm commented Jun 6, 2024

fixes #434

Copy link

codecov bot commented Jun 6, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.41%. Comparing base (e432c2f) to head (2249cc1).
Report is 57 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #436      +/-   ##
==========================================
+ Coverage   97.40%   97.41%   +0.01%     
==========================================
  Files          33       33              
  Lines       11102    11118      +16     
==========================================
+ Hits        10814    10831      +17     
+ Misses        288      287       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@biojppm biojppm force-pushed the fix/434-deserialize_bad_vals branch 2 times, most recently from 0139399 to b2e0a59 Compare June 7, 2024 19:12
@biojppm biojppm force-pushed the fix/434-deserialize_bad_vals branch from b2e0a59 to 2249cc1 Compare June 8, 2024 08:53
@biojppm biojppm merged commit 95866e8 into master Jun 8, 2024
244 of 246 checks passed
@biojppm biojppm deleted the fix/434-deserialize_bad_vals branch June 8, 2024 11:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unexpected behavior when deserializing to double
1 participant