All notable changes to this project will be documented in this file, in reverse chronological order by release.
- Nothing.
- Nothing.
- Nothing.
- Nothing.
- #58 adds a new
Uuidvalidator, capable of validating if Versions 1-5 UUIDs are well-formed. - #64 ports
Zend\ModuleManager\Feature\ValidatorProviderInterfacetoZend\Validator\ValidatorProviderInterface, and updates theModule::init()to typehint against the new interface instead of the one from zend-modulemanager. Applications targeting zend-mvc v3 can start updating their code to implement the new interface, or simply duck-type against it.
- Nothing.
- Nothing.
- Nothing.
- #67 adds support
for Punycoded top-level domains in the
Hostnamevalidator. - #79 adds and publishes the documentation to https://zendframework.github.io/zend-validator/
- Nothing.
- Nothing.
- Nothing.
- Nothing.
- Nothing.
- Nothing.
- #65 fixes the
Module::init()method to properly receive aModuleManagerinstance, and not expect aModuleEvent.
- Nothing.
- Nothing.
- Nothing.
- This release updates the TLD list to the latest version from the IANA.
- #63 exposes the
package as a ZF component and/or generic configuration provider, by adding the
following:
ValidatorPluginManagerFactory, which can be consumed by container-interop / zend-servicemanager to create and return aValidatorPluginManagerinstance.ConfigProvider, which maps the serviceValidatorManagerto the above factory.Module, which does the same asConfigProvider, but specifically for zend-mvc applications. It also provices a specification toZend\ModuleManager\Listener\ServiceListenerto allow modules to provide validator configuration.
- Nothing.
- Nothing.
- Nothing.
- #18 adds a
GpsPointvalidator for validating GPS coordinates. - #47 adds two new
classes,
Zend\Validator\Isbn\Isbn10andIsbn13; these classes are the result of an extract class refactoring, and contain the logic specific to calcualting the checksum for each ISBN style.Zend\Validator\Isbnnow instantiates the appropriate one and invokes it. - #46 updates
Zend\Validator\Db\AbstractDbto implementZend\Db\Adapter\AdapterAwareInterface, by composingZend\Db\Adapter\AdapterAwareTrait.
- Nothing.
- #55 removes some
checks for
safe_modewithin theMimeTypevalidator, assafe_modebecame obsolete starting with PHP 5.4.
- #45 fixes aliases
mapping the deprecated
FloatandIntvalidators to theirIs*counterparts. - #49 #50, and #51 update the code to be forwards-compatible with zend-servicemanager and zend-stdlib v3.
- #56 fixes the regex
in the
Ipvalidator to escape.characters used as IP delimiters.
- Nothing.
- Nothing.
- Nothing.
- #44 corrects the
grammar on the
NOT_GREATER_INCLUSIVEvalidation error message. - #45 adds normalized aliases for the i18n isfloat/isint validators.
- Updates the hostname validator regexes per the canonical service on which they are based.
- #52 updates the
Barcodevalidator to cast empty options passed to the constructor to an empty array, fixing type mismatch errors. - #54 fixes the IP
address detection in the
Hostnamevalidator to ensure that IPv6 is detected correctly. - #56 updates the
regexes used by the
IPvalidator when comparing ipv4 addresses to ensure a literal.is tested between network segments.
- #30 adds tooling to ensure that the Hostname TLD list stays up-to-date as changes are pushed for the repository.
- Nothing.
- Nothing.
- #17 and #29 provide more test coverage, and fix a number of edge cases, primarily in validator option verifications.
- #26 fixes tests for
StaticValidatorsuch that they make correct assertions now. In doing so, we determined that it was possible to pass an indexed array of options, which could lead to unexpected results, often leading to false positives when validating. To correct this situation,StaticValidator::execute()now raises anInvalidArgumentExceptionwhen an indexed array is detected for the$optionsargument. - #35 modifies the
NotEmptyvalidator to no longer treat the float0.0as an empty value for purposes of validation. - #25 fixes the
Datevalidator to check againstDateTimeImmutableand notDateTimeInterface(as PHP has restrictions currently on how the latter can be used).
- #8 adds a "strict" configuration option; when enabled (the default), the length of the address is checked to ensure it follows the specification.
- Nothing.
- Nothing.