Skip to content

Multi level Input-object validation issue #1168

Open
@morkers

Description

@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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions