[fix-validation-result] Fix validation result if nested input filters… #17
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
… get provided
When i was using an InputFilter with a nested CollectionInputFilter i saw that this ValidationResult tries to use CollectionFilter::getName, which causes an error because the property $invalidInputs of the CollectionInputFilter can also return InputFilterInterface[]
however this ValidationResult only works if you get InputInterface[].
fortunately the index variable of this foreach always contains the name that is needed for this ValidationResult.
the interfaces dont seem to fit together perfectly, see laminas/laminas-inputfilter#22 by func0der