Perl::Critic::Policy::Catalyst::ProhibitUnreachableCode - Don't write code after an unconditional Catalyst detach.
This module was forked from Perl::Critic::Policy::ControlStructures::ProhibitUnreachableCode version
1.132 and modified to fit.
The primary difference is this module looks for these two Catalyst specific bits of code as signifying a terminating statement:
redirect_and_detach context method is available if you are using Catalyst::Plugin::RedirectAndDetach.
By default this policy looks for the
redirect_and_detach context methods. You can specify additional context methods to look for with the
context_methods parameter. In your
.perlcriticrc this would look something like:
[Catalyst::ProhibitUnreachableCode] context_methods = my_detaching_method my_other_detaching_method
This policy would then consider all of the following lines as terminating statements:
$c->detach(); $c->redirect_and_detach(); $c->my_detaching_method(); $c->my_other_detaching_method();
Sometimes controllers have in-house methods which call
detach, you can specify those:
[Catalyst::ProhibitUnreachableCode] controller_methods = foo bar
Then this policy would look for any package with
::Controller:: in its name and would consider the following lines as terminating statements:
There are no default methods for this parameter.
Please submit bugs and feature requests to the Perl-Critic-Policy-Catalyst-ProhibitUnreachableCode GitHub issue tracker:
Aran Clary Deltac <email@example.com> Peter Guzis <firstname.lastname@example.org>
Thanks to ZipRecruiter for encouraging their employees to contribute back to the open source ecosystem. Without their dedication to quality software development this distribution would not exist.
This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.