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

better error messages #30

Merged
merged 3 commits into from
Sep 10, 2024
Merged

better error messages #30

merged 3 commits into from
Sep 10, 2024

Conversation

ccoVeille
Copy link
Owner

@ccoVeille ccoVeille commented Sep 9, 2024

  • fix: float overflow when converted to integer
  • feat: add meaningful error messages
  • doc: update documentation as errors messages changed

Fix #15

README.md Outdated Show resolved Hide resolved
Copy link

codecov bot commented Sep 10, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (c6327a9) to head (618c455).
Report is 3 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #30   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            2         3    +1     
  Lines           90       114   +24     
=========================================
+ Hits            90       114   +24     

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

@ldemailly
Copy link
Collaborator

mentioned on slack that math.MinInt32 for instance shouldn't be rejected

but from doc and error message point if view lgtm

@ccoVeille ccoVeille merged commit f90e86b into main Sep 10, 2024
3 checks passed
@ccoVeille ccoVeille deleted the better-error branch September 10, 2024 20:41
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.

consider using a struct for the error type
2 participants