Skip Menu |

This queue is for tickets about the Moose CPAN distribution.

Report information
The Basics
Id: 99362
Status: rejected
Priority: 0/
Queue: Moose
People
Owner: Nobody in particular
Requestors: NNUTTER [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: 2.1213
Fixed in: (no value)

History Show all quoted text
  Tue Oct 07 16:54:23 2014 NNUTTER [...] cpan.org - Ticket created
Subject: Moose::Manual example does not follow Moose::Manual::BestPractices
The Moose::Manual ends a package/class with 'no Moose;' but the Moose::Manual::BestPractices recommends using 'use namespace::autoclean;' instead of 'no Moose;'.
  Tue Oct 07 16:55:16 2014 DROLSKY [...] cpan.org - Correspondence added
On Tue Oct 07 16:54:23 2014, NNUTTER wrote: Show quoted text
> The Moose::Manual ends a package/class with 'no Moose;' but the > Moose::Manual::BestPractices recommends using 'use > namespace::autoclean;' instead of 'no Moose;'.
Heh, this is a good point, but I'm not sure using modules that don't ship with Moose itself in the core manual docs is a good idea.
  Tue Oct 07 16:55:16 2014 The RT System itself - Status changed from 'new' to 'open'
  Tue Oct 07 17:27:18 2014 NNUTTER [...] cpan.org - Correspondence added
On Tue Oct 07 16:55:16 2014, DROLSKY wrote: Show quoted text
> On Tue Oct 07 16:54:23 2014, NNUTTER wrote:
> > The Moose::Manual ends a package/class with 'no Moose;' but the > > Moose::Manual::BestPractices recommends using 'use > > namespace::autoclean;' instead of 'no Moose;'.
> > Heh, this is a good point, but I'm not sure using modules that don't > ship with Moose itself in the core manual docs is a good idea.
Yeah, I realized after I submitted that namespace::autoclean wasn't a dependency.
  Tue Oct 07 18:04:53 2014 NNUTTER [...] cpan.org - Correspondence added
Rejecting my own ticket since it doesn't make sense for Moose docs to have implicit dependencies.
  Tue Oct 07 18:04:54 2014 NNUTTER [...] cpan.org - Status changed from 'open' to 'rejected'