1 package Perl::Critic::Policy::DynamicMoose::ClassOverridesRole;
3 extends 'Perl::Critic::Policy::DynamicMoose';
5 use Perl::Critic::Utils ':severities';
7 Readonly::Scalar my $EXPL => q{Explicitly exclude overriden methods};
8 sub default_severity { $SEVERITY_MEDIUM }
10 # Class::MOP::Class has no roles
11 sub applies_to_metaclass { 'Moose::Meta::Class' }
13 sub violates_metaclass {
19 for my $application ($class->role_applications) {
20 my $role = $application->role;
21 for my $method ($role->get_method_list) {
22 next if $application->is_method_excluded($method);
23 next if $application->is_method_aliased($method);
25 my $method_object = $class->get_method($method)
28 # no metadata, should check source role to make sure it's the
30 if ($method_object->isa('Moose::Meta::Role::Method')) {
31 next if $method_object->original_package_name eq $role->name;
34 my $class_name = $class->name;
35 my $role_name = $role->name;
37 my $desc = "Class '$class_name' method '$method' implicitly overrides the same method from role '$role_name'";
38 push @violations, $self->violation($desc, $EXPL);
53 Perl::Critic::Policy::DynamicMoose::ClassOverridesRole
60 B<VERY IMPORTANT:> Most L<Perl::Critic> Policies (including all the ones that
61 ship with Perl::Critic> use pure static analysis -- they never compile nor
62 execute any of the code that they analyze. However, this policy is very
63 different. It actually attempts to compile your code and then compares the
64 subroutines mentioned in your code to those found in the symbol table.
65 Therefore you should B<not> use this Policy on any code that you do not trust,
66 or may have undesirable side-effects at compile-time (such as connecting to the
67 network or mutating files).
69 For this Policy to work, all the modules included in your code must be
70 installed locally, and must compile without error.
74 Shawn M Moore, C<sartak@bestpractical.com>