NAME
App::CriticDB::Collector - Collect Perl::Critic violations for files
VERSION
Version 0.0.4
SYNOPSIS
use App::CriticDB::Collector;
my $collector=App::CriticDB::Collector->new(
profile=>'path',
store =>sub { callback },
flush =>sub { callback },
newer =>sub { callback },
);
$collector->collect(@paths);DESCRIPTION
The Collector builds a Perl::Critic instance to retrieve violations at any severity and stores them via callback (to datastore providers).
Caveats
The collect defaults to the top one million violations per file.
CALLBACKS
Discovered violations are passed to a datastore via the configured callbacks.
Store
Store a list of violations associated with a file:
store(file=>'name',violations=>[...])The current time is stored as the mtime associated with the update. Depending on the datastore, updates may only be committed to memory.
Flush
Force the updates to be saved in the datastore. A datastore may queue updates from store to reduce overhead, but flush will ensure updates are committed.
Because violation storage includes the current mtime, results that are not committed will be rescanned by the collector on the next run.
Newer
If defined, files will be skipped if their current on-disk mtime is less than or equal to their mtime in the datastore. Files not in the datastore are always included.
TODO
The Collector should support all standard and reasonable perlcritic commandline options.
Provide a mode where files are always "newer" (forced rescan).
SEE ALSO
AUTHORS
Brian Blackmore (brian@mediaalpha.com).
COPYRIGHT
Copyright (c) 2025--2035, MediaAlpha.com.This library is free software; you can redistribute it and/or modify it under the terms of the GNU Library General Public License Version 3 as published by the Free Software Foundation.