lib/Ajde/Crud/Options/List/Buttons.php

Summary

Maintainability
A
35 mins
Test Coverage

Method addItemButton has 5 arguments (exceeds 4 allowed). Consider refactoring.
Open

    public function addItemButton($name, $text, $class = null, $persistent = false, $function = false)
Severity: Minor
Found in lib/Ajde/Crud/Options/List/Buttons.php - About 35 mins to fix

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

        public function addItemButton($name, $text, $class = null, $persistent = false, $function = false)

    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 addItemButton has a boolean flag argument $function, which is a certain sign of a Single Responsibility Principle violation.
    Open

        public function addItemButton($name, $text, $class = null, $persistent = false, $function = false)

    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 up has a boolean flag argument $obj, which is a certain sign of a Single Responsibility Principle violation.
    Open

        public function up($obj = false)

    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 unused parameters such as '$obj'.
    Open

        public function up($obj = false)

    UnusedFormalParameter

    Since: 0.2

    Avoid passing parameters to methods or constructors and then not using those parameters.

    Example

    class Foo
    {
        private function bar($howdy)
        {
            // $howdy is not used
        }
    }

    Source https://phpmd.org/rules/unusedcode.html#unusedformalparameter

    Avoid using short method names like Ajde_Crud_Options_List_Buttons::up(). The configured minimum method name length is 3.
    Open

        public function up($obj = false)
        {
            return parent::up($this);
        }

    ShortMethodName

    Since: 0.2

    Detects when very short method names are used.

    Example

    class ShortMethod {
        public function a( $index ) { // Violation
        }
    }

    Source https://phpmd.org/rules/naming.html#shortmethodname

    The class Ajde_Crud_Options_List_Buttons is not named in CamelCase.
    Open

    class Ajde_Crud_Options_List_Buttons extends Ajde_Crud_Options
    {
        /**
         * @return Ajde_Crud_Options_List
         */

    CamelCaseClassName

    Since: 0.2

    It is considered best practice to use the CamelCase notation to name classes.

    Example

    class class_name {
    }

    Source

    There are no issues that match your filters.

    Category
    Status