Multi level Input-object validation issue

[morkers]

Q	A
Bug report?	yes
Feature request?	no
BC Break report?	no
RFC?	no
Version/Branch	0.13.7

There seems to be an issue validating array of input-objects.

Having a simple mutation:

Mutation:
    type: object
    config:
        fields:
            testMutation:
                type: Boolean
                resolve: "@=mutation('testMutation', [args])"
                args:
                    fields:
                        type: '[TestInput]'
                        validation: cascade
TestInput:
    type: input-object
    config:
        fields:
            subField:
                type: SubTestInput
                validation: cascade

SubTestInput:
    type: input-object
    config:
        fields:
            price:
                type: Float
                validation:
                    -  Positive: ~

Then sending mutation i don't get the error i expect. The first SubTestInput is not validated.

mutation{
    testMutation(fields: [
        {
            subField: {
                price: -1
            }
        },
        {
        }
    ])
}

As the second/last TestInput does not have SubTestInput defined, validation metadata is overriden with metadata that doesn't have any constraints registered and validation for first SubTestInput is not done.

[Vincz]

I'm not familiar with the validator component. Maybe @murtukov can look into it?

[kedramon]

same for me, none of child validations run for array of input-object

[jsakars]

No updates on this?

[murtukov]

@Vincz @jsakars I will take a look at it today

[murtukov]

@jsakars @morkers a quick update: I investigated the issue and found the bug. I'll try to provide a fix in the following days