Upgrading from 10.1.1 to 10.2.0 input type error EXEC_INVALID_TYPE

[drowhunter]

Describe the bug Upgraded to 10.2.0 and suddenly my mutations give me the following error

To Reproduce Steps to reproduce the behavior:

{
    "errors": [{
        "message": "Variable `$input` got invalid value.",
        "locations": [{
            "line": 1,
            "column": 16
        }],
        "extensions": {
            "code": "EXEC_INVALID_TYPE",
            "remote": {
                "Exception": null,
                "message": "Variable `$input` got invalid value.",
                "locations": [{
                    "line": 1,
                    "column": 16
                }],
                "extensions": {
                    "code": "EXEC_INVALID_TYPE"
                }
            }
        }
    }],
    "data": {
        "addUserBloodSugarTrackerDataPoint": null
    }
}

Additional context Rolling back to 10.1.1 fixes the issue

[michaelstaib]

Can you provide more information. With 10.2.0 we fixed a validation bug, that mean variables now have to be of the correct type now. Before that we were for instance skipping invalid fields.

[drowhunter]

I have an object called input which is a custom poco class

public class AddWeightTrackerGoalInput
    {
        public double BodyWeight { get; set; }
        public int WeightUnit { get; set; }
    }

which has the following Type defined and registered

public class AddWeightTrackerGoalInputType : InputObjectType<AddWeightTrackerGoalInput>
    {
        protected override void Configure(IInputObjectTypeDescriptor<AddWeightTrackerGoalInput> descriptor)
        {

        }
    }

the query looks like this

"mutation ($input: AddWeightTrackerGoalInput) {
  addWeightTrackerGoal(input: $input) {
    ... fragment
  }
}
"

The Input is defined as

and the input variable passed is like

{
"input":{"bodyWeight": 80, "weightUnit": 2}
}
``

[michaelstaib]

Can you trace out the request that is send between the gateway and the domain service?

[drowhunter]

im actually not using the gateway. I went directly to the api itself to run the query the example i passed earlier wasnt that great I was on my phone. Here is a better example of what isn't working. Now you can see the InputType Definition and the input parameters that are being passed.

[drowhunter]

Actually looks like we are passing decimals to a parameter that is expecting Int. I assume that in the previous version you were not actually validating these fields

[michaelstaib]

@drowhunter yeah that's it. The spec defines that you can put an int into a float but not the reverse way. We now enforce these rules.

[michaelstaib]

I will close this issue since this is now working as expected.