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

Added rounding mode param to divide method #135

Merged

Conversation

Sword-of-GraySkull
Copy link
Contributor

@Sword-of-GraySkull Sword-of-GraySkull commented Jun 23, 2024

Since the divide method lacks the rounding mode parameter, this line defaults the rounding to (HALF EVEN)

Hence, adding the rounding mode param to round the result of divide method to be rounded with other rounding options

@Sword-of-GraySkull Sword-of-GraySkull force-pushed the patch_divide_rounding_mode branch from e95b5b6 to 028237d Compare June 23, 2024 09:36
Copy link
Collaborator

@Jsoto22 Jsoto22 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good enhancement, simple implementation, and includes UT.

@Sword-of-GraySkull Sword-of-GraySkull force-pushed the patch_divide_rounding_mode branch from 028237d to 06c9b91 Compare June 24, 2024 12:58
@Sword-of-GraySkull Sword-of-GraySkull force-pushed the patch_divide_rounding_mode branch from 06c9b91 to c608d9e Compare June 24, 2024 13:08
@Sword-of-GraySkull
Copy link
Contributor Author

@Jsoto22 Can you please rerun the workflows?

@Jsoto22 Jsoto22 merged commit efbe456 into royNiladri:master Jun 25, 2024
4 checks passed
@Sword-of-GraySkull
Copy link
Contributor Author

@Jsoto22

npm-publish job seems to have not published the package. Because is_version is returned as false in the 'Check if tag is a version' step. Could you please assist?

@Jsoto22
Copy link
Collaborator

Jsoto22 commented Jun 25, 2024

I'm currently looking into a few things I noticed come up in the workflow. I'll get back to you when I can.

@Sword-of-GraySkull
Copy link
Contributor Author

@Jsoto22 @royNiladri

Have you been able to look up the npm-publish job failure?

I can see that you are looking for any difference between the last published npm version and the latest git tag for the publish step to happen. But, I couldn't figure out when the new tag was created.

@Jsoto22
Copy link
Collaborator

Jsoto22 commented Jul 7, 2024

Sorry, haven't had much time since. I'll prep a release to create the missing tag tomorrow if I can.

@Sword-of-GraySkull
Copy link
Contributor Author

Sword-of-GraySkull commented Jul 13, 2024

Hey @Jsoto22 , I understand you're likely busy. But I wanted to follow up on the release request. Thanks for your time

@royNiladri
Copy link
Owner

royNiladri commented Jul 14, 2024 via email

@Sword-of-GraySkull
Copy link
Contributor Author

Thanks, @royNiladri for the update. I have manually updated the version from 2.0.7 to 2.0.8 in package.json. So, I believe we shouldn't bump the version with npm version minor again. Can you create a tag for 2.0.8 and publish it for now?

@Sword-of-GraySkull
Copy link
Contributor Author

@royNiladri

As mentioned, Could you create a tag for 2.0.8 and publish the version?

@royNiladri
Copy link
Owner

Hi @Sword-of-GraySkull & @Jsoto22,
Sorry for the delayed response. I have updated the Readme, and published a
minor version update! v2.1.0
image

Cheer🥳

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.

3 participants