Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Perl-Critic CPAN distribution.

Report information
The Basics
Id: 20163
Status: rejected
Priority: 0/
Queue: Perl-Critic
People
Owner: Nobody in particular
Requestors: a.ford [...] ford-mason.co.uk
Cc:
AdminCc:
Bug Information
Severity: Wishlist
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Wed Jun 28 09:17:25 2006 ANDREWF [...] cpan.org - Ticket created
Subject: add an option to perlcritic to display de-duped explanations of all violations
It would be useful if perlcritic could optionally output a de-duplicated list of the explanations of all violated policies at the end of its report. Having the explanation output for each violation is much too verbose (severity set to 9 or 10), but not having the description to hand can be too cryptic (any other predefined severity). Looks like this feature could be implemented simply by scanning @violations in the for loop in critique() in the perlcritic script, building up the set of policies violated and then outputting that set after the loop (if the summary option was specified). I could supply a patch if you are interested.
  Wed Jun 28 09:57:04 2006 ANDREWF [...] cpan.org - Correspondence added
Subject: add an option to perlcritic to display de-duped discussions of all violations
On Wed Jun 28 09:17:25 2006, ANDREWF wrote: Show quoted text
> It would be useful if perlcritic could optionally output a de-duplicated > list of the explanations of all violated policies at the end of its > report. Having the explanation output for each violation is much too > verbose (severity set to 9 or 10), but not having the description to > hand can be too cryptic (any other predefined severity). > > Looks like this feature could be implemented simply by scanning > @violations in the for loop in critique() in the perlcritic script, > building up the set of policies violated and then outputting that set > after the loop (if the summary option was specified). > > I could supply a patch if you are interested.
To clarify: I meant "full diagnostic discussions" (%d escapes) rather than explanation/PBP page numbers (%e escapes). The intent is that the report is followed by a glossary of the violations.
  Wed Jun 28 09:57:05 2006 The RT System itself - Status changed from 'new' to 'open'
  Thu Sep 20 02:38:17 2007 thaljef [...] cpan.org - Correspondence added
I don't think we will implement this feature. As an alternative, this is one way to get the full documentation on all the policies that have been violated in a particular file (in bash). for policy in `perlcritic -v '%p\n' SomeFile.pm | sort -u`; do perldoc Perl::Critic::Policy::$policy; done
  Thu Sep 20 02:38:19 2007 thaljef [...] cpan.org - Status changed from 'open' to 'rejected'