It seems to stem from this gem's use of the Oj library and this configuration that's applied when you call the AvaTax::API#connection method. Our solution was to just pull that configuration out, and everything worked as expected. But I was curious as to why it's included in the first place? Is it safe to do some kind of conditional check to make sure we're not in Ruby v2.2+ before applying this config?
After updating to avatax v17.12 we noticed tests failing that made use of JSON and BigDecimal, like so:
It seems to stem from this gem's use of the
Oj
library and this configuration that's applied when you call theAvaTax::API#connection
method. Our solution was to just pull that configuration out, and everything worked as expected. But I was curious as to why it's included in the first place? Is it safe to do some kind of conditional check to make sure we're not in Ruby v2.2+ before applying this config?