Maks3w
Maks3w
I start to think the best option could be to have 2 validator chains. One for validate the data and another one for validate the input state. Something like this...
For to make this works seems It's needed a flag for "break the chain on success" for the ValidatorChain and create an OptionalValidator. Thoughts? I think its reasonable to have...
I don't see this as a BC Break because the translation feature seems never has work. Anyway the purpose of this PR is discuss about the required / optional field...
@stefanotorresi Prior to 2.5.2/2.4.5 there was not a required message.
I keep thinking in new ways for make this better. Probably with something like #87
Code coverage drop its for a difference between phpunit code coverage versions.
I'm not sure if continue with this or rewrite the component. There is not urgency for to merge this
Chain can be created from static methods and added to input filters ``` php $inputFilter->addInput("input name", Chain $chain); $result = $inputFilter->resolve($inputValuesArray); $result->isValid(); $result->getValues(); ``` About the code legibility this is...
Note this way of make chains could replace or remove ValidatorChain and FilterChain classes
Well, who said this things could not be async in the future or with alternative PHP engines.