yiisoft /
validator
| Conditions | 3 |
| Paths | 2 |
| Total Lines | 56 |
| Code Lines | 2 |
| Lines | 0 |
| Ratio | 0 % |
| Tests | 2 |
| CRAP Score | 3.3332 |
| 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:
Methods with many parameters are not only hard to understand, but their parameters also often become inconsistent when you need more, or different data.
There are several approaches to avoid long parameter lists:
| 1 | <?php |
||
| 32 | 3 | public function __construct( |
|
| 33 | #[Language('RegExp')] |
||
| 34 | /** |
||
| 35 | * @var string the regular expression used to validate value. |
||
| 36 | * |
||
| 37 | * @link http://www.regular-expressions.info/email.html |
||
| 38 | */ |
||
| 39 | private string $pattern = '/^[a-zA-Z0-9!#$%&\'*+\\/=?^_`{|}~-]+(?:\.[a-zA-Z0-9!#$%&\'*+\\/=?^_`{|}~-]+)*@(?:[a-zA-Z0-9](?:[a-zA-Z0-9-]*[a-zA-Z0-9])?\.)+[a-zA-Z0-9](?:[a-zA-Z0-9-]*[a-zA-Z0-9])?$/', |
||
| 40 | #[Language('RegExp')] |
||
| 41 | /** |
||
| 42 | * @var string the regular expression used to validate email addresses with the name part. This property is used |
||
| 43 | * only when {@see $allowName} is `true`. |
||
| 44 | * |
||
| 45 | * @see $allowName |
||
| 46 | */ |
||
| 47 | private string $fullPattern = '/^[^@]*<[a-zA-Z0-9!#$%&\'*+\\/=?^_`{|}~-]+(?:\.[a-zA-Z0-9!#$%&\'*+\\/=?^_`{|}~-]+)*@(?:[a-zA-Z0-9](?:[a-zA-Z0-9-]*[a-zA-Z0-9])?\.)+[a-zA-Z0-9](?:[a-zA-Z0-9-]*[a-zA-Z0-9])?>$/', |
||
| 48 | #[Language('RegExp')] |
||
| 49 | /** |
||
| 50 | * @var string the regular expression used to validate complex emails when {@see $enableIDN} is `true`. |
||
| 51 | */ |
||
| 52 | private string $idnEmailPattern = '/^([a-zA-Z0-9._%+-]+)@((\[\d{1,3}\.\d{1,3}\.\d{1,3}\.)|(([\w-]+\.)+))([a-zA-Z]{2,4}|\d{1,3})(\]?)$/', |
||
| 53 | /** |
||
| 54 | * @var bool whether to allow name in the email address (e.g. "John Smith <[email protected]>"). Defaults |
||
| 55 | * to `false`. |
||
| 56 | * |
||
| 57 | * @see $fullPattern |
||
| 58 | */ |
||
| 59 | private bool $allowName = false, |
||
| 60 | /** |
||
| 61 | * @var bool whether to check whether the email's domain exists and has either an A or MX record. |
||
| 62 | * Be aware that this check can fail due to temporary DNS problems even if the email address is |
||
| 63 | * valid and an email would be deliverable. Defaults to `false`. |
||
| 64 | */ |
||
| 65 | private bool $checkDNS = false, |
||
| 66 | /** |
||
| 67 | * @var bool whether validation process should take into account IDN (internationalized domain |
||
| 68 | * names). Defaults to false meaning that validation of emails containing IDN will always fail. |
||
| 69 | * Note that in order to use IDN validation you have to install and enable `intl` PHP extension, |
||
| 70 | * otherwise an exception would be thrown. |
||
| 71 | */ |
||
| 72 | private bool $enableIDN = false, |
||
| 73 | private string $incorrectInputMessage = 'The value must have a string type.', |
||
| 74 | private string $message = 'This value is not a valid email address.', |
||
| 75 | |||
| 76 | /** |
||
| 77 | * @var bool|callable|null |
||
| 78 | */ |
||
| 79 | private $skipOnEmpty = null, |
||
| 80 | private bool $skipOnError = false, |
||
| 81 | /** |
||
| 82 | * @var Closure(mixed, ValidationContext):bool|null |
||
| 83 | */ |
||
| 84 | private ?Closure $when = null, |
||
| 85 | 3 | ) { |
|
| 86 | if ($enableIDN && !function_exists('idn_to_ascii')) { |
||
| 87 | throw new RuntimeException('In order to use IDN validation intl extension must be installed and enabled.'); |
||
| 88 | } |
||
| 161 |
