php-xapi /
repository-doctrine
| Conditions | 19 |
| Paths | 13 |
| Total Lines | 52 |
| Code Lines | 26 |
| Lines | 0 |
| Ratio | 0 % |
| Changes | 1 | ||
| Bugs | 0 | Features | 0 |
Small methods make your code easier to understand, in particular if combined with a good name. Besides, if your method is small, finding a good name is usually much easier.
For example, if you find yourself adding comments to a method's body, this is usually a good sign to extract the commented part to a new method, and use the comment as a starting point when coming up with a good name for this new method.
Commonly applied refactorings include:
If many parameters/temporary variables are present:
| 1 | <?php |
||
| 123 | public function assertMappedStatement(MappedStatement $expected, MappedStatement $actual) |
||
| 124 | { |
||
| 125 | if ($expected->id !== $actual->id) { |
||
| 126 | return false; |
||
| 127 | } |
||
| 128 | |||
| 129 | if (!$expected->actor->equals($actual->actor)) { |
||
| 130 | return false; |
||
| 131 | } |
||
| 132 | |||
| 133 | if (!$expected->verb->equals($actual->verb)) { |
||
| 134 | return false; |
||
| 135 | } |
||
| 136 | |||
| 137 | if (!$expected->object->equals($actual->object)) { |
||
| 138 | return false; |
||
| 139 | } |
||
| 140 | |||
| 141 | if (null === $expected->result && null !== $actual->result) { |
||
| 142 | return false; |
||
| 143 | } |
||
| 144 | |||
| 145 | if (null !== $expected->result && null === $actual->result) { |
||
| 146 | return false; |
||
| 147 | } |
||
| 148 | |||
| 149 | if (null !== $expected->result && !$expected->result->equals($actual->result)) { |
||
| 150 | return false; |
||
| 151 | } |
||
| 152 | |||
| 153 | if (null === $expected->authority && null !== $actual->authority) { |
||
| 154 | return false; |
||
| 155 | } |
||
| 156 | |||
| 157 | if (null !== $expected->authority && null === $actual->authority) { |
||
| 158 | return false; |
||
| 159 | } |
||
| 160 | |||
| 161 | if (null !== $expected->authority && !$expected->authority->equals($actual->authority)) { |
||
| 162 | return false; |
||
| 163 | } |
||
| 164 | |||
| 165 | if ($expected->created != $actual->created) { |
||
| 166 | return false; |
||
| 167 | } |
||
| 168 | |||
| 169 | if (null === $actual->stored) { |
||
| 170 | return false; |
||
| 171 | } |
||
| 172 | |||
| 173 | return true; |
||
| 174 | } |
||
| 175 | } |
||
| 176 |
Loading history...
Our type inference engine has found a suspicous assignment of a value to a property. This check raises an issue when a value that can be of a mixed type is assigned to a property that is type hinted more strictly.
For example, imagine you have a variable
$accountIdthat can either hold an Id object or false (if there is no account id yet). Your code now assigns that value to theidproperty of an instance of theAccountclass. This class holds a proper account, so the id value must no longer be false.Either this assignment is in error or a type check should be added for that assignment.