cmpayments /
json-schema-validator
| Conditions | 5 |
| Paths | 4 |
| Total Lines | 14 |
| Code Lines | 5 |
| Lines | 0 |
| Ratio | 0 % |
| Changes | 0 | ||
| 1 | <?php namespace CMPayments\SchemaValidator\Validators; |
||
| 20 | public function validateString($data, $schema, $path) |
||
| 21 | { |
||
| 22 | // check for $schema->minLength |
||
|
|
|||
| 23 | if (isset($schema->minLength) && (($currentLength = strlen($data)) < $schema->minLength)) { |
||
| 24 | |||
| 25 | $this->addError(ValidateException::ERROR_USER_STRING_MINIMUM_CHECK, [$path, $schema->minLength, $data, $currentLength]); |
||
| 26 | } |
||
| 27 | |||
| 28 | // check for $schema->maxLength |
||
| 29 | if (isset($schema->maxLength) && (($currentLength = strlen($data)) > $schema->maxLength)) { |
||
| 30 | |||
| 31 | $this->addError(ValidateException::ERROR_USER_STRING_MAXIMUM_CHECK, [$path, $schema->maxLength, $data, $currentLength]); |
||
| 32 | } |
||
| 33 | } |
||
| 34 | |||
| 42 | } |
Loading history...
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.