Apigiltiy uses integer indexed arrays and nested input_filter_specs only work with associative arrays!
In Apigility I have a code-connected resource with an embedded collection of items. For validation I defined an input_filter_spec with a nested CollectionInputFilter using associative arrays.
Problems started when I manually defined this filter in zf-content-validation for the resource. At first integration worked perfect except there where no fields visible in Apigility but the filter worked incl. the embedded items. But when I added a field it removed all the input_filter_specs of the filter.
Next I defined my filter using an integer-index and the filter stopped working on the embedded items because the nested input filter has no name property.
This patch tries to solve this by allowing input_filter_specs to have a name entry.
To minimize side effects or possible BC breaks the name is used only on integer indexed specs with a type defined and the name itself is a string.
A side effect of the patch is Apigility shows all fields but silently breaks (Angular exception) when trying to add a filter. Adding a validator works but is faulty. It should not be difficult to prevent Apigility from modifying fields with nested filters. Developers of resources with nested entities will be helped and are already used to do manual changes.
Apigiltiy uses integer indexed arrays and nested
input_filter_specsonly work with associative arrays!In Apigility I have a code-connected resource with an embedded collection of items. For validation I defined an
input_filter_specwith a nestedCollectionInputFilterusing associative arrays. Problems started when I manually defined this filter inzf-content-validationfor the resource. At first integration worked perfect except there where no fields visible in Apigility but the filter worked incl. the embedded items. But when I added a field it removed all theinput_filter_specsof the filter. Next I defined my filter using an integer-index and the filter stopped working on the embedded items because the nested input filter has no name property.This patch tries to solve this by allowing
input_filter_specsto have anameentry.To minimize side effects or possible BC breaks the name is used only on integer indexed specs with a
typedefined and the name itself is a string.A side effect of the patch is Apigility shows all fields but silently breaks (Angular exception) when trying to add a filter. Adding a validator works but is faulty. It should not be difficult to prevent Apigility from modifying fields with nested filters. Developers of resources with nested entities will be helped and are already used to do manual changes.