src/Model/Property/AbstractProperty.php
The method getAttribute has a boolean flag argument $variableName, which is a certain sign of a Single Responsibility Principle violation. Open
Open
public function getAttribute(bool $variableName = false): string
- Read upRead up
- Exclude checks
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 using static access to class '\PHPModelGenerator\Utils\NormalizedName' in method 'processAttributeName'. Open
Open
return lcfirst(NormalizedName::from($name, $this->jsonSchema));
- Read upRead up
- Exclude checks
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
Rename "$attribute" which has the same name as the field declared at line 25. Open
Open
$attribute = !$this->isInternal() && $variableName && preg_match('/^\d/', $this->attribute) === 1
- Read upRead up
- Exclude checks
Shadowing fields with a local variable is a bad practice that reduces code readability: it makes it confusing to know whether the field or the variable is being used.
Noncompliant Code Example
class Foo { public $myField; public function doSomething() { $myField = 0; ... } }
See
- CERT, DCL51-J. - Do not shadow or obscure identifiers in subscopes