| Conditions | 8 |
| Paths | 48 |
| Total Lines | 57 |
| Code Lines | 31 |
| Lines | 28 |
| Ratio | 49.12 % |
| 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 |
||
| 82 | public function saveSettings($namespace, Settings $settings) |
||
| 83 | { |
||
| 84 | $schema = $this->schemaRegistry->getSchema($namespace); |
||
| 85 | |||
| 86 | $settingsBuilder = new SettingsBuilder(); |
||
| 87 | $schema->buildSettings($settingsBuilder); |
||
| 88 | |||
| 89 | $parameters = $settingsBuilder->resolve($settings->getParameters()); |
||
| 90 | |||
| 91 | View Code Duplication | foreach ($settingsBuilder->getTransformers() as $parameter => $transformer) { |
|
| 92 | if (array_key_exists($parameter, $parameters)) { |
||
| 93 | $parameters[$parameter] = $transformer->transform($parameters[$parameter]); |
||
| 94 | } |
||
| 95 | } |
||
| 96 | |||
| 97 | if (isset($this->resolvedSettings[$namespace])) { |
||
| 98 | $this->resolvedSettings[$namespace]->setParameters($parameters); |
||
| 99 | } |
||
| 100 | |||
| 101 | $persistedParameters = $this->parameterRepository->findBy( |
||
| 102 | array('category' => $namespace, 'cId' => $this->getCourse()->getId()) |
||
| 103 | ); |
||
| 104 | |||
| 105 | $persistedParametersMap = array(); |
||
| 106 | |||
| 107 | foreach ($persistedParameters as $parameter) { |
||
| 108 | $persistedParametersMap[$parameter->getName()] = $parameter; |
||
| 109 | } |
||
| 110 | |||
| 111 | View Code Duplication | foreach ($parameters as $name => $value) { |
|
| 112 | if (isset($persistedParametersMap[$name])) { |
||
| 113 | $persistedParametersMap[$name]->setValue($value); |
||
| 114 | } else { |
||
| 115 | /** @var CCourseSetting $parameter */ |
||
| 116 | //$parameter = $this->parameterFactory->createNew(); |
||
| 117 | $parameter = new CCourseSetting(); |
||
| 118 | $parameter |
||
| 119 | ->setNamespace($namespace) |
||
| 120 | ->setName($name) |
||
| 121 | ->setValue($value) |
||
| 122 | ->setCId($this->getCourse()->getId()) |
||
| 123 | ; |
||
| 124 | |||
| 125 | /* @var $errors ConstraintViolationListInterface */ |
||
| 126 | $errors = $this->validator->validate($parameter); |
||
| 127 | if (0 < $errors->count()) { |
||
| 128 | throw new ValidatorException($errors->get(0)->getMessage()); |
||
| 129 | } |
||
| 130 | |||
| 131 | $this->parameterManager->persist($parameter); |
||
| 132 | } |
||
| 133 | } |
||
| 134 | |||
| 135 | $this->parameterManager->flush(); |
||
| 136 | |||
| 137 | $this->cache->save($namespace, $parameters); |
||
| 138 | } |
||
| 139 | |||
| 157 |
Overwriting private methods is generally fine as long as you also use private visibility. It might still be preferable for understandability to use a different method name.