rhosocial/yii2-base-models

View on GitHub
traits/MultipleBlameableTrait.php

Summary

Maintainability
A
3 hrs
Test Coverage

File MultipleBlameableTrait.php has 254 lines of code (exceeds 250 allowed). Consider refactoring.
Open

<?php

/**
 *  _   __ __ _____ _____ ___  ____  _____
 * | | / // // ___//_  _//   ||  __||_   _|
Severity: Minor
Found in traits/MultipleBlameableTrait.php - About 2 hrs to fix

    Function addOrCreateBlame has a Cognitive Complexity of 10 (exceeds 5 allowed). Consider refactoring.
    Open

        public function addOrCreateBlame(&$blame = null, $user = null)
        {
            if (!is_string($this->multiBlamesClass)) {
                throw new InvalidConfigException
                ('$multiBlamesClass must be specified if you want to use multiple blameable features.');
    Severity: Minor
    Found in traits/MultipleBlameableTrait.php - About 1 hr to fix

    Cognitive Complexity

    Cognitive Complexity is a measure of how difficult a unit of code is to intuitively understand. Unlike Cyclomatic Complexity, which determines how difficult your code will be to test, Cognitive Complexity tells you how difficult your code will be to read and comprehend.

    A method's cognitive complexity is based on a few simple rules:

    • Code is not considered more complex when it uses shorthand that the language provides for collapsing multiple statements into one
    • Code is considered more complex for each "break in the linear flow of the code"
    • Code is considered more complex when "flow breaking structures are nested"

    Further reading

    The method getBlameGuids has a boolean flag argument $checkValid, which is a certain sign of a Single Responsibility Principle violation.
    Open

        public function getBlameGuids($checkValid = false)
    Severity: Minor
    Found in traits/MultipleBlameableTrait.php by phpmd

    BooleanArgumentFlag

    Since: 1.4.0

    A boolean flag argument is a reliable indicator for a violation of the Single Responsibility Principle (SRP). You can fix this problem by extracting the logic in the boolean flag into its own class or method.

    Example

    class Foo {
        public function bar($flag = true) {
        }
    }

    Source https://phpmd.org/rules/cleancode.html#booleanargumentflag

    The method setBlameGuids has a boolean flag argument $checkValid, which is a certain sign of a Single Responsibility Principle violation.
    Open

        public function setBlameGuids($guids = [], $checkValid = true)
    Severity: Minor
    Found in traits/MultipleBlameableTrait.php by phpmd

    BooleanArgumentFlag

    Since: 1.4.0

    A boolean flag argument is a reliable indicator for a violation of the Single Responsibility Principle (SRP). You can fix this problem by extracting the logic in the boolean flag into its own class or method.

    Example

    class Foo {
        public function bar($flag = true) {
        }
    }

    Source https://phpmd.org/rules/cleancode.html#booleanargumentflag

    Avoid assigning values to variables in if clauses and the like (line '191', column '14').
    Open

        public function addOrCreateBlame(&$blame = null, $user = null)
        {
            if (!is_string($this->multiBlamesClass)) {
                throw new InvalidConfigException
                ('$multiBlamesClass must be specified if you want to use multiple blameable features.');
    Severity: Minor
    Found in traits/MultipleBlameableTrait.php by phpmd

    IfStatementAssignment

    Since: 2.7.0

    Assignments in if clauses and the like are considered a code smell. Assignments in PHP return the right operand as their result. In many cases, this is an expected behavior, but can lead to many difficult to spot bugs, especially when the right operand could result in zero, null or an empty string and the like.

    Example

    class Foo
    {
        public function bar($flag)
        {
            if ($foo = 'bar') { // possible typo
                // ...
            }
            if ($baz = 0) { // always false
                // ...
            }
        }
    }

    Source http://phpmd.org/rules/cleancode.html#ifstatementassignment

    Avoid assigning values to variables in if clauses and the like (line '215', column '14').
    Open

        public function removeBlame($blame)
        {
            if (!is_string($this->multiBlamesAttribute)) {
                return false;
            }
    Severity: Minor
    Found in traits/MultipleBlameableTrait.php by phpmd

    IfStatementAssignment

    Since: 2.7.0

    Assignments in if clauses and the like are considered a code smell. Assignments in PHP return the right operand as their result. In many cases, this is an expected behavior, but can lead to many difficult to spot bugs, especially when the right operand could result in zero, null or an empty string and the like.

    Example

    class Foo
    {
        public function bar($flag)
        {
            if ($foo = 'bar') { // possible typo
                // ...
            }
            if ($baz = 0) { // always false
                // ...
            }
        }
    }

    Source http://phpmd.org/rules/cleancode.html#ifstatementassignment

    Closing parenthesis of a multi-line function call must be on a line by itself
    Open

                ('$multiBlamesClass must be specified if you want to use multiple blameable features.');

    Space before opening parenthesis of function call prohibited
    Open

                throw new InvalidConfigException

    Opening parenthesis of a multi-line function call must be the last content on the line
    Open

                throw new InvalidConfigException

    There are no issues that match your filters.

    Category
    Status