Per a forum post the validators config key is not honored currently unless the application is within a zend-mvc context. This is due to the fact that Zend\Validator\Module wires configuration for the Zend\ModuleManager\Listener\ServiceListener in order to push merged service configuration into the plugin during bootstrap; no similar logic is available when not in a zend-mvc context, however.
This patch fixes that situation by modifying the ValidatorPluginManagerFactory to do the following:
If a ServiceListener service exists, it returns the plugin manager immediately (old behavior).
Otherwise, it checks for the config service, and, if found, a validators key with an array value. When found, it feeds that value to a Zend\ServiceManager\Config instance and uses that to configure the plugin manager before returning it.
Per a forum post the
validatorsconfig key is not honored currently unless the application is within a zend-mvc context. This is due to the fact thatZend\Validator\Modulewires configuration for theZend\ModuleManager\Listener\ServiceListenerin order to push merged service configuration into the plugin during bootstrap; no similar logic is available when not in a zend-mvc context, however.This patch fixes that situation by modifying the
ValidatorPluginManagerFactoryto do the following:ServiceListenerservice exists, it returns the plugin manager immediately (old behavior).configservice, and, if found, avalidatorskey with an array value. When found, it feeds that value to aZend\ServiceManager\Configinstance and uses that to configure the plugin manager before returning it.