[TRINIDAD-1683] client-side convertNumber causes loss of precision

• Type: Bug
• Status: Reopened
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 1.2.12-core
• Fix Version/s: 1.2.15-core
• Component/s: Components
• Assignee: Gabrielle Crawford
• Reporter: Cale Scholl
• Created: 08/Jan/10 23:56
• Updated: 14/Jan/11 15:03

Description

ISSUE:
----------

JS numbers are 64-bit values and thus only have 16 digits of precision; this isn't enough to represent the max value of a Long, BigInteger, or BigDecimal. This means that when we convert a number string to object then back to string on the client, we can lose precision, even though we wouldn't lose any precision on the server.

FIX:

---

Only render a client converter if the input value is bound to a supported type (Float, Double, Integer, Short, Byte). The JavaScript number is a 64-bit floating type and has enough precision to represent any of these supported types.