Any chance you'd consider switching your JSON dependency to MultiJson? This allows the user to decide the JSON implementation themselves, while still allowing json_pure as an option for those that want it.
The reason for this is that json_pure defines ::JSON and is not always API compatible with other implementations. If another gem uses a different library that also defines ::JSON, the two implementations can fight and slightly different behaviours can occur. Including Chargebee in the project has caused a lot of JSON errors elsewhere for me because of issues like this.
Hi,
Any chance you'd consider switching your JSON dependency to MultiJson? This allows the user to decide the JSON implementation themselves, while still allowing json_pure as an option for those that want it.
The reason for this is that
json_pure
defines::JSON
and is not always API compatible with other implementations. If another gem uses a different library that also defines::JSON
, the two implementations can fight and slightly different behaviours can occur. Including Chargebee in the project has caused a lot of JSON errors elsewhere for me because of issues like this.