qcubed/framework

View on GitHub
install/project/includes/controls/QSampleControl.class.php

Summary

Maintainability
A
0 mins
Test Coverage

Avoid using static access to class 'QType' in method '__set'.
Open

                        return ($this->strFoo = QType::Cast($mixValue, QType::String));

StaticAccess

Since: 1.4.0

Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.

Example

class Foo
{
    public function bar()
    {
        Bar::baz();
    }
}

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

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

        public function GetControlHtml() {
            // Pull any Attributes
            $strAttributes = $this->GetAttributes();

            // Pull any styles

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 using static access to class 'QType' in method '__set'.
Open

                        return ($this->intExample = QType::Cast($mixValue, QType::Integer));

StaticAccess

Since: 1.4.0

Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.

Example

class Foo
{
    public function bar()
    {
        Bar::baz();
    }
}

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

The method ParsePostData is not named in camelCase.
Open

        public function ParsePostData() {}

CamelCaseMethodName

Since: 0.2

It is considered best practice to use the camelCase notation to name methods.

Example

class ClassName {
    public function get_name() {
    }
}

Source

The method Validate is not named in camelCase.
Open

        public function Validate() {return true;}

CamelCaseMethodName

Since: 0.2

It is considered best practice to use the camelCase notation to name methods.

Example

class ClassName {
    public function get_name() {
    }
}

Source

The method GetControlHtml is not named in camelCase.
Open

        public function GetControlHtml() {
            // Pull any Attributes
            $strAttributes = $this->GetAttributes();

            // Pull any styles

CamelCaseMethodName

Since: 0.2

It is considered best practice to use the camelCase notation to name methods.

Example

class ClassName {
    public function get_name() {
    }
}

Source

There are no issues that match your filters.

Category
Status