Fix Bug related to IEEE 754

[leomotors]

The Bug

This bug happens for every number that ends with .29, .57, .58

Because when these numbers are multiplied by 100, they become

The issue is at rounding down the Satang to 2 digits which cause the inaccuracy

This pull request

• ✅ Fix for String
• ✅ Fix for Small Number (<1000)
• ✅ Fix for Big Number (>100000)
• ➕ Added Test Cases to ensure those 3 are fixed, and also added test cases to other parts to ensure this change doesn't break the library

String

Before:

satang = satangStr ? Math.floor(Number('0.' + satangStr) * 100) : 0;

After:

satang = satangStr
  ? Number(satangStr.slice(0, 2)) *
      (satangStr.length >= 2 ? 1 : [100, 10][satangStr.length])
  : 0;

This will fix for all strings, and it also appeared to be a bit faster than before

Number

Before:

satang = Number.isInteger(input)
  ? 0 
  : Math.floor((input * 100) % 100);

After:

satang = Number.isInteger(input)
  ? 0
  : Math.floor(((input + Number.EPSILON * (baht || 1)) * 100) % 100);

This will now fix for most of the numbers, theoretically, it should work up to around 10^12-14
For performance, based on the benchmark, it does not have much difference.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/notnarze/baht-js/2RK2gr642feC4GXZUteUUtbWS1JH
✅ Preview: https://baht-js-git-fork-leomotors-main-notnarze.vercel.app

[narze]

🙏🏻

This will be released as v0.7.0

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information