range: Fix getting decimal part of numbers close to 0

[obiwac]

New Pull Request

Previously, isFloat was being called on val before noExponents. This meant that if a value was particularly close to zero, it might pass the isFloat check but then be stripped down to just 0 by noExponents, which meant that getting the second element after splitting around the decimal point would fail.

This patch just does noExponent first so that if the value ends up being a round number, it doesn't enter that branch.

Type of change

• Bug fix (non-breaking change which fixes an issue)

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• My branch is up to date with any changes from the main branch

[mjchang]

Thanks - coincidentally just encountered this too #4911