Skip Menu |

This queue is for tickets about the MetaCPAN-API CPAN distribution.

Report information
The Basics
Id: 96973
Status: rejected
Priority: 0/
Queue: MetaCPAN-API

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: Use of deprecated Any::Moose
As documented, this is now deprecated in favour of Moo - see http://shadow.cat/blog/matt-s-trout/moo-versus-any-moose/ for an explanation of why Any::Moose is broken by design. https://metacpan.org/pod/Any::Moose#DEPRECATION
On Sat Jul 05 22:56:37 2014, ETHER wrote: Show quoted text
> As documented, this is now deprecated in favour of Moo - see > http://shadow.cat/blog/matt-s-trout/moo-versus-any-moose/ for an > explanation of why Any::Moose is broken by design. > > https://metacpan.org/pod/Any::Moose#DEPRECATION
MetaCPAN::API is already deprecated itself.
Subject: Re: [rt.cpan.org #96973] Use of deprecated Any::Moose
Date: Sun, 6 Jul 2014 08:48:44 -0700
To: Sawyer X via RT <bug-MetaCPAN-API [...] rt.cpan.org>
From: Karen Etheridge <ether [...] cpan.org>
On Sun, Jul 06, 2014 at 05:46:39AM -0400, Sawyer X via RT wrote: Show quoted text
> MetaCPAN::API is already deprecated itself.
Could you possibly add that to the abstract (the =head1 NAME bit of pod), as well as include a link in the documentation that points to the new version of the API? It's not at all clear that it's deprecated. I'd send a PR, but I can't find the proper name of the new thing. :)