apie-lib /
openapi-schema
| 1 | <?php |
||
| 2 | |||
| 3 | namespace Apie\OpenapiSchema\Map; |
||
| 4 | |||
| 5 | use Apie\CompositeValueObjects\Exceptions\InvalidKeyException; |
||
| 6 | use Apie\CompositeValueObjects\ValueObjectHashmapTrait; |
||
| 7 | use Apie\CompositeValueObjects\ValueObjectListInterface; |
||
| 8 | use Apie\TypeJuggling\StringLiteral; |
||
| 9 | use Apie\TypeJuggling\TypeUtilInterface; |
||
| 10 | |||
| 11 | class ScopesMap implements ValueObjectListInterface |
||
| 12 | { |
||
| 13 | use ValueObjectHashmapTrait; |
||
| 14 | |||
| 15 | protected static function getWantedType(string $fieldName): TypeUtilInterface |
||
| 16 | { |
||
| 17 | if (!preg_match('/^[a-zA-Z][a-zA-Z:0-9]*$/', $fieldName)) { |
||
| 18 | throw new InvalidKeyException($fieldName); |
||
|
0 ignored issues
–
show
|
|||
| 19 | } |
||
| 20 | return new StringLiteral($fieldName); |
||
| 21 | } |
||
| 22 | } |
||
| 23 |
This check compares calls to functions or methods with their respective definitions. If the call has less 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. Please note the @ignore annotation hint above.