| Conditions | 10 | 
| Paths | 3 | 
| Total Lines | 9 | 
| Code Lines | 4 | 
| Lines | 0 | 
| Ratio | 0 % | 
| Changes | 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 | ||
| 56 | public function setAny($any = null): self | ||
| 57 |     { | ||
| 58 | // validation for constraint: xml | ||
| 59 |         if (!is_null($any) && !$any instanceof \DOMDocument && (!is_string($any) || (is_string($any) && (empty($any) || (($anyDoc = new \DOMDocument()) && false === $anyDoc->loadXML($any)))))) { | ||
| 60 |             throw new InvalidArgumentException(sprintf('Invalid value %s, please provide a valid XML string', var_export($any, true)), __LINE__); | ||
| 61 | } | ||
| 62 | $this->any = ($any instanceof \DOMDocument) ? $any->saveXML($any->hasChildNodes() ? $any->childNodes->item(0) : null) : $any; | ||
| 63 | |||
| 64 | return $this; | ||
| 65 | } | ||
| 67 |