fix(round): Throw an exception when precision
is not an integer
#79
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.
Description
When rounding, the type of the second parameter,
precision
, is Number, which can also accept float values. Therefore, I added exception handling for cases where it is not an Integer.Changes
When attempting to use the round function with inputs like round(1.2345, 3.1), the result was 1.2343860767615331, which does not behave as desired for a rounding function. To fix this, I added exception handling with the following code.
This ensures that the
precision
parameter must be an integer, preventing incorrect rounding behavior.