sonata-project /
SonataAdminBundle
| Conditions | 11 |
| Paths | 24 |
| Total Lines | 56 |
| 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 |
||
| 72 | public function addAdminClassAces( |
||
| 73 | OutputInterface $output, |
||
| 74 | AclInterface $acl, |
||
| 75 | AclSecurityHandlerInterface $securityHandler, |
||
| 76 | array $roleInformation = [] |
||
| 77 | ) { |
||
| 78 | if (!$acl instanceof MutableAclInterface) { |
||
| 79 | throw new \TypeError(sprintf( |
||
|
|
|||
| 80 | 'Argument 2 passed to "%s()" must implement "%s".', |
||
| 81 | __METHOD__, |
||
| 82 | MutableAclInterface::class |
||
| 83 | )); |
||
| 84 | } |
||
| 85 | if (\count($securityHandler->getAdminPermissions()) > 0) { |
||
| 86 | $builder = new $this->maskBuilderClass(); |
||
| 87 | |||
| 88 | foreach ($roleInformation as $role => $permissions) { |
||
| 89 | $aceIndex = $securityHandler->findClassAceIndexByRole($acl, $role); |
||
| 90 | $roleAdminPermissions = []; |
||
| 91 | |||
| 92 | foreach ($permissions as $permission) { |
||
| 93 | // add only the admin permissions |
||
| 94 | if (\in_array($permission, $securityHandler->getAdminPermissions(), true)) { |
||
| 95 | $builder->add($permission); |
||
| 96 | $roleAdminPermissions[] = $permission; |
||
| 97 | } |
||
| 98 | } |
||
| 99 | |||
| 100 | if (\count($roleAdminPermissions) > 0) { |
||
| 101 | if (false === $aceIndex) { |
||
| 102 | $acl->insertClassAce(new RoleSecurityIdentity($role), $builder->get()); |
||
| 103 | $action = 'add'; |
||
| 104 | } else { |
||
| 105 | $acl->updateClassAce($aceIndex, $builder->get()); |
||
| 106 | $action = 'update'; |
||
| 107 | } |
||
| 108 | |||
| 109 | if (null !== $output) { |
||
| 110 | $output->writeln(sprintf(' - %s role: %s, permissions: %s', $action, $role, json_encode($roleAdminPermissions))); |
||
| 111 | } |
||
| 112 | |||
| 113 | $builder->reset(); |
||
| 114 | } elseif (false !== $aceIndex) { |
||
| 115 | $acl->deleteClassAce($aceIndex); |
||
| 116 | |||
| 117 | if (null !== $output) { |
||
| 118 | $output->writeln(sprintf(' - remove role: %s', $role)); |
||
| 119 | } |
||
| 120 | } |
||
| 121 | } |
||
| 122 | |||
| 123 | return true; |
||
| 124 | } |
||
| 125 | |||
| 126 | return false; |
||
| 127 | } |
||
| 128 | } |
||
| 129 |
This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.
If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.
In this case you can add the
@ignorePhpDoc annotation to the duplicate definition and it will be ignored.