Tags: DragonBe/zend-validator
Tags
zend-validator 2.12.0 Added ----- - [zendframework#250](zendframework#250) adds support for PHP 7.3. Changed ------- - [zendframework#251](zendframework#251) updates the logic of each of the various `Zend\Validator\File` validators to allow validating against PSR-7 `UploadedFileInterface` instances, expanding the support originally provided in version 2.11.0. Deprecated ---------- - Nothing. Removed ------- - [zendframework#250](zendframework#250) removes support for zend-stdlib v2 releases. Fixed ----- - Nothing.
zend-validator 2.11.1 Added ----- - [zendframework#249](zendframework#249) adds support in the hostname validator for the `.rs` TLD. Changed ------- - [zendframework#253](zendframework#253) updates the list of allowed characters for a `DE` domain name to match those published by IDN. Deprecated ---------- - Nothing. Removed ------- - Nothing. Fixed ----- - [zendframework#256](zendframework#256) fixes hostname validation when omitting the TLD from verification, ensuring validation of the domain segment considers all URI criteria.
zend-validator 2.11.0 Added ----- - [zendframework#237](zendframework#237) adds support for the [PSR-7 UploadedFileInterface](https://www.php-fig.org/psr/psr-7/#uploadedfileinterface) to each of the `Upload` and `UploadFile` validators. - [zendframework#220](zendframework#220) adds image/webp to the list of known image types for the `IsImage` validator. Changed ------- - Nothing. Deprecated ---------- - Nothing. Removed ------- - Nothing. Fixed ----- - Nothing.
zend-validator 2.10.3 Added ----- - Nothing. Changed ------- - Nothing. Deprecated ---------- - Nothing. Removed ------- - Nothing. Fixed ----- - [zendframework#241](zendframework#241) has the `Hostname` validator return an invalid result early when an empty domain segment is detected. - [zendframework#232](zendframework#232) updates the `Hostname` validator to allow underscores in subdomains. - [zendframework#218](zendframework#218) fixes a precision issue with the `Step` validator.
zend-validator 2.10.2 Added ----- - [zendframework#202](zendframework#202) adds the ability to use custom constant types in extensions of `Zend\Validator\CreditCard`, fixing an issue where users were unable to add new brands as they are created. - [zendframework#203](zendframework#203) adds support for the new Russian bank card "Mir". - [zendframework#204](zendframework#204) adds support to the IBAN validator for performing SEPA validation against Croatia and San Marino. - [zendframework#209](zendframework#209) adds documentation for the `Explode` validator. Changed ------- - Nothing. Deprecated ---------- - Nothing. Removed ------- - Nothing. Fixed ----- - [zendframework#195](zendframework#195) adds missing `GpsPoint` validator entries to the `ValidatorPluginManager`, ensuring they may be retrieved from it correctly. - [zendframework#212](zendframework#212) updates the `CSRF` validator to automatically mark any non-string values as invalid, preventing errors such as array to string conversion.
zend-validator 2.10.1 Added ----- - Nothing. Changed ------- - Nothing. Deprecated ---------- - Nothing. Removed ------- - Nothing. Fixed ----- - [zendframework#194](zendframework#194) modifies the `EmailAddress` validator to omit the `INTL_IDNA_VARIANT_UTS46` flag to `idn_to_utf8()` if the constant is not defined, fixing an issue on systems using pre-2012 releases of libicu.
zend-validator 2.10.0 Added ----- - [zendframework#175](zendframework#175) adds support for PHP 7.2 (conditionally, as PHP 7.2 is currently in beta1). - [zendframework#157](zendframework#157) adds a new validator, `IsCountable`, which allows validating: - if a value is countable - if a countable value exactly matches a configured count - if a countable value is greater than a configured minimum count - if a countable value is less than a configured maximum count - if a countable value is between configured minimum and maximum counts Changed ------- - [zendframework#169](zendframework#169) modifies how the various `File` validators check for readable files. Previously, they used `stream_resolve_include_path`, which led to false negative checks when the files did not exist within an `include_path` (which is often the case within a web application). These now use `is_readable()` instead. - [zendframework#185](zendframework#185) updates the zend-session requirement (during development, and in the suggestions) to 2.8+, to ensure compatibility with the upcoming PHP 7.2 release. - [zendframework#187](zendframework#187) updates the `Between` validator to **require** that both a `min` and a `max` value are provided to the constructor, and that both are of the same type (both integer/float values and/or both string values). This fixes issues that could previously occur when one or the other was not set, but means an exception will now be raised during instantiation (versus runtime during `isValid()`). - [zendframework#188](zendframework#188) updates the `ConfigProvider` to alias the service name `ValidatorManager` to the class `Zend\Validator\ValidatorPluginManager`, and now maps the the latter class to the `ValidatorPluginManagerFactory`. Previously, we mapped the service name directly to the factory. Usage should not change for anybody at this point. Deprecated ---------- - Nothing. Removed ------- - [zendframework#175](zendframework#175) removes support for HHVM. Fixed ----- - [zendframework#160](zendframework#160) fixes how the `EmailAddress` validator handles the local part of an address, allowing it to support unicode.
zend-validator 2.9.2 Added ----- - Nothing. Deprecated ---------- - Nothing. Removed ------- - Nothing. Fixed ----- - [zendframework#180](zendframework#180) fixes how `Zend\Validator\File\MimeType` "closes" the open FileInfo handle for the file being validated, using `unset()` instead of `finfo_close()`; this resolves a segfault that occurs on older PHP versions. - [zendframework#174](zendframework#174) fixes how `Zend\Validator\Between` handles two situations: (1) when a non-numeric value is validated against numeric min/max values, and (2) when a numeric value is validated against non-numeric min/max values. Previously, these incorrectly validated as true; now they are marked invalid.
PreviousNext