Conversion from JsonNumber to BigDecimal can throw exceptions about circe HOT 3 CLOSED

I think your range is too large

This specification allows implementations to set limits on the range and precision of numbers accepted. Since software that implements IEEE 754-2008 binary64 (double precision) numbers [IEEE754] is generally available and widely used, good interoperability can be achieved by implementations that expect no more precision or range than these provide, in the sense that implementations will approximate JSON numbers within the expected precision.
http://rfc7159.net/rfc7159#rfc.section.6

https://en.wikipedia.org/wiki/Double-precision_floating-point_format#Double-precision_examples

from circe.

@etaty Agreed that this isn't 100% necessary in any sense, but we're building a JSON library, not a processor, and it'd be nice to be able to represent losslessly as many valid JSON values as reasonably possible.

from circe.

Fixed in #189.

from circe.