Skip Menu |

This queue is for tickets about the I22r-Translate CPAN distribution.

Report information
The Basics
Id: 116635
Status: open
Priority: 0/
Queue: I22r-Translate

People
Owner: Nobody in particular
Requestors: ether [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: JSON::Any is being phased out
JSON::Any is being phased out in favour of JSON::MaybeXS, which handles the edge cases more gracefully - you probably want to switch to that, unless you rely on some of the legacy stuff (e.g. JSON::DWIM and ::Syck support) in JSON::Any.
On Mon Aug 01 14:32:27 2016, ETHER wrote: Show quoted text
> JSON::Any is being phased out in favour of JSON::MaybeXS, which > handles the edge cases more gracefully - you probably want to switch > to that, unless you rely on some of the legacy stuff (e.g. JSON::DWIM > and ::Syck support) in JSON::Any.
I'm tempted to reject this. There are tests in my distribution that expect $json->decode(...) to return a decoded string, but when I use JSON::MaybeXS this returns a UTF-8 encoded string. -- MO'B
On 2016-08-07 17:22:43, MOB wrote: Show quoted text
> I'm tempted to reject this. There are tests in my distribution that > expect $json->decode(...) to > return a decoded string, but when I use JSON::MaybeXS > this returns a UTF-8 encoded string.
use JSON::MaybeXS; my $str = JSON()->new(utf8 => 0)->decode($other_str); JSON::Any got the utf8 defaults backwards from how they actually are in (Cpanel::)?JSON::XS.