view release on metacpan or  search on metacpan

META.json  view on Meta::CPAN

				"Module::Build::Tiny": "0.040"
			}
		},
		"runtime": {
			"requires": {
				"perl": "0",
				"Carp": "0",
				"Perl::Critic": "0"
			},
			"suggests": {
				"Data::Dumper": "2.183",
				"File::Temp": "0.2301",
				"Getopt::Long": "2.58",
				"Pod::Usage": "1.64",
				"Storable": "0"
			}
		},
		"test": {
			"requires": {
				"File::Temp": "0.2301",
				"PPI": "0",

lib/App/CriticDB.pm  view on Meta::CPAN

=head2 File

L<Perl::Critic> violations may be stored in a local file:

  my $criticdb=App::CriticDB->new(file=>'violations.stor',type=>'storable');
  $criticdb->collect('/path/to/lib');

The C<type> may be:

  storable   Storable (default)
  dump       Data::Dumper (not yet available)

Note that L<Data::Dumper> files can be useful for debugging purposes but are not recommended for long term use, as they can be 10--30x slower for read/write operations.

=head1 REPORTING

Output similar to C<perlcritic> can be produced by calling as

  $criticdb->report(verbose=>'... format ...')

This supports both numeric and the string format specifiers from C<perlcritic>.

Currently only reporting to STDOUT is supported.