cross-solution /
YAWIK
| Conditions | 5 |
| Paths | 1 |
| Total Lines | 64 |
| Code Lines | 36 |
| 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 |
||
| 40 | public function __invoke(ContainerInterface $container, $requestedName, array $options = null) |
||
| 41 | { |
||
| 42 | |||
| 43 | $fieldset = new EmployeeFieldset(); |
||
| 44 | |||
| 45 | $hydrator = new \Zend\Hydrator\ClassMethods(false); //new EntityHydrator(); |
||
|
|
|||
| 46 | $repositories = $container->get('repositories'); |
||
| 47 | $users = $repositories->get('Auth/User'); /* @var $users \Auth\Repository\User */ |
||
| 48 | |||
| 49 | /* todo: WRITE own Hydrator strategy class */ |
||
| 50 | $strategy = new ClosureStrategy( |
||
| 51 | function ($object) use ($users) { |
||
| 52 | |||
| 53 | if (is_string($object)) { |
||
| 54 | return $users->find($object); |
||
| 55 | } |
||
| 56 | return $object; |
||
| 57 | }, |
||
| 58 | function ($data) use ($users) { |
||
| 59 | |||
| 60 | if (is_string($data)) { |
||
| 61 | $data = $users->find($data); |
||
| 62 | } |
||
| 63 | return $data; |
||
| 64 | } |
||
| 65 | ); |
||
| 66 | |||
| 67 | /* todo: write own strategy class */ |
||
| 68 | $permStrategy = new ClosureStrategy( |
||
| 69 | // extract |
||
| 70 | function ($object) { |
||
| 71 | /* @var $object \Organizations\Entity\EmployeePermissionsInterface */ |
||
| 72 | $values = array(); |
||
| 73 | foreach (array( |
||
| 74 | Perms::JOBS_VIEW, Perms::JOBS_CHANGE, PERMS::JOBS_CREATE, |
||
| 75 | Perms::APPLICATIONS_VIEW, Perms::APPLICATIONS_CHANGE) |
||
| 76 | as $perm) { |
||
| 77 | if ($object->isAllowed($perm)) { |
||
| 78 | $values[] = $perm; |
||
| 79 | } |
||
| 80 | |||
| 81 | } |
||
| 82 | |||
| 83 | return $values; |
||
| 84 | }, |
||
| 85 | function ($data) { |
||
| 86 | $permissions = array_reduce( |
||
| 87 | $data, |
||
| 88 | function ($c, $i) { |
||
| 89 | return $c | $i; |
||
| 90 | }, |
||
| 91 | 0 |
||
| 92 | ); |
||
| 93 | return new EmployeePermissions($permissions); |
||
| 94 | } |
||
| 95 | ); |
||
| 96 | |||
| 97 | $hydrator->addStrategy('user', $strategy); |
||
| 98 | $hydrator->addStrategy('permissions', $permStrategy); |
||
| 99 | $fieldset->setHydrator($hydrator); |
||
| 100 | $fieldset->setObject(new \Organizations\Entity\Employee()); |
||
| 101 | |||
| 102 | return $fieldset; |
||
| 103 | } |
||
| 104 | |||
| 117 | } |
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.
The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.
This check looks for comments that seem to be mostly valid code and reports them.