gesdinet /
JWTRefreshTokenBundle
| Conditions | 3 |
| Paths | 3 |
| Total Lines | 17 |
| Lines | 0 |
| Ratio | 0 % |
| Tests | 0 |
| CRAP Score | 12 |
| Changes | 0 | ||
| 1 | <?php |
||
| 18 | public function process(ContainerBuilder $container) |
||
| 19 | { |
||
| 20 | $customUserProvider = $container->getParameter('gesdinet_jwt_refresh_token.user_provider'); |
||
| 21 | if (!$customUserProvider) { |
||
| 22 | return; |
||
| 23 | } |
||
| 24 | if (!$container->hasDefinition('gesdinet.jwtrefreshtoken.user_provider')) { |
||
| 25 | return; |
||
| 26 | } |
||
| 27 | |||
| 28 | $definition = $container->getDefinition('gesdinet.jwtrefreshtoken.user_provider'); |
||
| 29 | |||
| 30 | $definition->addMethodCall( |
||
| 31 | 'setCustomUserProvider', |
||
| 32 | array(new Reference($customUserProvider, ContainerInterface::NULL_ON_INVALID_REFERENCE, false)) |
||
|
|
|||
| 33 | ); |
||
| 34 | } |
||
| 35 | } |
||
| 36 |
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.