Skip Menu |
 

This queue is for tickets about the JSON-Any CPAN distribution.

Report information
The Basics
Id: 82016
Status: resolved
Priority: 0/
Queue: JSON-Any

People
Owner: Nobody in particular
Requestors: ribasushi [...] leporine.io
Cc:
AdminCc:

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



Subject: Support for JSON::PP
Download (untitled) / with headers
text/plain 413b
The DEPRECATION section states the following "mission statement": JSON::Any will continue to be maintained for compatibility with existing code, and frankly because the maintainer prefers the JSON::Any API. In light of that will you be interested in patches to add a 'PP' JSON provider which will correspond to JSON::PP? I would provide patches etc, just asking ahead of time if there is interest in this at all.
Subject: Re: [rt.cpan.org #82016] Support for JSON::PP
Date: Wed, 19 Dec 2012 12:43:10 -0800
To: Peter Rabbitson via RT <bug-JSON-Any [...] rt.cpan.org>
From: Karen Etheridge <ether [...] cpan.org>
Download (untitled) / with headers
text/plain 311b
On Sun, Dec 16, 2012 at 05:56:48AM -0500, Peter Rabbitson via RT wrote: Show quoted text
> In light of that will you be interested in patches to add a 'PP' JSON > provider which will correspond to JSON::PP? I would provide patches etc, > just asking ahead of time if there is interest in this at all.
That sounds great to me!
Download (untitled) / with headers
text/plain 139b
Please confirm that this is still an issue in 1.31 and above. I added tests for JSON::PP and they're passing so I think we fixed support :)
Download (untitled) / with headers
text/plain 159b
Yep, everything seems to work well, and the extended DBIC test is happy too: https://github.com/dbsrgits/dbix-class/commit/be855469#diff-2 Marking as resolved


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.