Fix inconsistent typing of duration properties#1265
Merged
Conversation
MaxAake
force-pushed
the
fix-integer-conversion-with-configs
branch
from
967c612 to
f433d5c
Compare
robsdedude
reviewed
Jun 5, 2025
robsdedude
approved these changes
Jun 10, 2025
Member
robsdedude
left a comment
robsdedude
left a comment
There was a problem hiding this comment.
Optional nit: the fact that your last commits changed behavior while all tests stayed the same (and passed before and still do) suggests that test coverage could be improved :)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When creating a Duration the seconds and nanoseconds will be converted to Integers, no matter if provided with Integers, Numbers, or BigInts. This is awkward and requires special handling by users