Fix days to hours boundary for precise delta #19
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #14
Changes proposed in this pull request:
precisedelta
truncate
flag to truncate and remove values too close to zero inprecisedelta
Note: I don't feel that
truncate
is the correct name and I think that it could be easily misinterpreted. We need a better name.This PR also does not include a documentation for this flag nor tests (but a file in
tests/issue-14-days-hours-boundary-in-precisedelta.md
describes and tests all the cases discussed in #14 so it can be used as the base for an unit test and/or as the tests themselves running them with byexample )Closes #14