Conditions | 9 |
Paths | 8 |
Total Lines | 53 |
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 |
||
49 | public function resolve( |
||
50 | FieldDescriptionInterface $fieldDescription, |
||
51 | ModelManagerInterface $modelManager |
||
52 | ): ?DataTransformerInterface { |
||
53 | $dataTransformer = $fieldDescription->getOption('data_transformer'); |
||
54 | |||
55 | // allow override predefined transformers for 'date', 'boolean' and 'choice' field types |
||
56 | if ($dataTransformer instanceof DataTransformerInterface) { |
||
57 | return $dataTransformer; |
||
58 | } |
||
59 | |||
60 | $fieldType = (string) $fieldDescription->getType(); |
||
61 | |||
62 | // allow override predefined transformers on a global level |
||
63 | if (\array_key_exists($fieldType, $this->globalCustomTransformers)) { |
||
64 | return $this->globalCustomTransformers[$fieldType]; |
||
65 | } |
||
66 | |||
67 | // Handle date type has setter expect a DateTime object |
||
68 | if (TemplateRegistry::TYPE_DATE === $fieldType) { |
||
69 | $this->globalCustomTransformers[$fieldType] = new DateTimeToStringTransformer(null, null, 'Y-m-d'); |
||
70 | |||
71 | return $this->globalCustomTransformers[$fieldType]; |
||
72 | } |
||
73 | |||
74 | // Handle datetime type has setter expect a DateTime object |
||
75 | if (TemplateRegistry::TYPE_DATETIME === $fieldType) { |
||
76 | $this->globalCustomTransformers[$fieldType] = new DateTimeToStringTransformer(null, null, 'Y-m-d H:i:s'); |
||
77 | |||
78 | return $this->globalCustomTransformers[$fieldType]; |
||
79 | } |
||
80 | |||
81 | // Handle boolean type transforming the value into a boolean |
||
82 | if (TemplateRegistry::TYPE_BOOLEAN === $fieldType) { |
||
83 | $this->globalCustomTransformers[$fieldType] = new BooleanToStringTransformer('1'); |
||
84 | |||
85 | return $this->globalCustomTransformers[$fieldType]; |
||
86 | } |
||
87 | |||
88 | // Handle entity choice association type, transforming the value into entity |
||
89 | if (TemplateRegistry::TYPE_CHOICE === $fieldType) { |
||
90 | $className = $fieldDescription->getOption('class'); |
||
91 | |||
92 | if (null !== $className && |
||
93 | // NEXT_MAJOR: Replace this call with "$className === $fieldDescription->getTargetModel()". |
||
94 | $this->hasFieldDescriptionAssociationWithClass($fieldDescription, $className) |
||
95 | ) { |
||
96 | return new ModelToIdTransformer($modelManager, $className); |
||
97 | } |
||
98 | } |
||
99 | |||
100 | return null; |
||
101 | } |
||
102 | |||
112 |
Let’s take a look at an example:
In the above example, the authenticate() method works fine as long as you just pass instances of MyUser. However, if you now also want to pass a different implementation of User which does not have a getDisplayName() method, the code will break.
Available Fixes
Change the type-hint for the parameter:
Add an additional type-check:
Add the method to the interface: