Mutation with complex field types

[robertionut95b]

Hello,

I have the following scenario where I want to push a Mutation with the following types:

Input used

input OrganizationInput {
    id: Long
    name: String! @constraint(minLength: 3)
    slogan: String! @constraint(minLength: 5, maxLength: 100)
    description: String! @constraint(minLength: 5)
    activitySectorId: Long! @constraint(minLength: 1)
    headQuartersId: Long! @constraint(minLength: 1)
    photography: String
    webSite: Url
    foundedAt: Date!
    companySize: OrganizationSize
    locations: [Long]
    specializations: [Specialization]
}

Mutation

type Mutation {
...
createOrUpdateOrganization(OrganizationInput: OrganizationInput!): Organization
}

I try to submit a sample request with the body below:

{
  "query": "\n    mutation CreateOrUpdateOrganization($OrganizationInput: OrganizationInput!) {\n  createOrUpdateOrganization(OrganizationInput: $OrganizationInput) {\n    name\n    description\n  }\n}\n    ",
  "variables": {
    "OrganizationInput": {
      "id": 1,
      "name": "Paxton",
      "description": "Paxton is the perfect place to find your dream career. With our easy-to-use platform, you can search for jobs based on your skills and experience. We also have a wide range of resources to help you prepare for your job search. So what are you waiting for? Start your job search today",
      "slogan": "Find your perfect career with Paxton.",
      "activitySectorId": 1,
      "headQuartersId": 2,
      "companySize": "BETWEEN_1_5",
      "foundedAt": "2022-10-01",
      "webSite": "...",
      "specializations": [
        "IT_and_Software",
        "AI",
        "Software_Development",
        "Software_Product_Design",
        "Project_Management"
      ],
      "locations": [
        2,
        3
      ],
      "photography": "...."
    }
  },
  "operationName": "CreateOrUpdateOrganization"
}

How should the nested complex types like numeric arrays be included in an Input argument? On the server side, I get the following error but I am uncertain what is the conflicting field specifically:

org.springframework.core.convert.ConversionFailedException: Failed to convert from type [java.util.LinkedHashMap<?, ?>] to type [@com.netflix.graphql.dgs.InputArgument com.irb.paxton.core.organization.input.OrganizationInput] for value [{...}]
	at org.springframework.core.convert.support.ConversionUtils.invokeConverter(ConversionUtils.java:47) ~[spring-core-6.0.12.jar:6.0.12]
	at org.springframework.core.convert.support.GenericConversionService.convert(GenericConversionService.java:192) ~[spring-core-6.0.12.jar:6.0.12]
	at com.netflix.graphql.dgs.internal.method.AbstractInputArgumentResolver.convertValue(AbstractInputArgumentResolver.kt:79) ~[graphql-dgs-7.5.3.jar:7.5.3]
	at com.netflix.graphql.dgs.internal.method.AbstractInputArgumentResolver.resolveArgument(AbstractInputArgumentResolver.kt:48) ~[graphql-dgs-7.5.3.jar:7.5.3]

The mutation resolver method is just:

@DgsMutation
    public Organization createOrUpdateOrganization(@InputArgument OrganizationInput OrganizationInput) {
        return this.organizationService.createOrUpdateOrganization(OrganizationInput);
    }

[congotej]

Hey @robertionut95b ! I think the issue may be with your operation input itself, not with the implementation details on the server, i.e not DGS framework related.

Looks like there's an issue with converting the input argument OrganizationInput in your GraphQL mutation resolver. Specifically in the arrays (locations and specializations) within the OrganizationInput object.

locations and specializations are defined as arrays of Long and Specialization respectively. However, the input variables you're providing in your request JSON do not match this. You are using plain integers and strings instead of arrays.

Try something like this instead:

{
  "query": "mutation CreateOrUpdateOrganization($OrganizationInput: OrganizationInput!) {\n  createOrUpdateOrganization(OrganizationInput: $OrganizationInput) {\n    name\n    description\n  }\n}\n",
  "variables": {
    "OrganizationInput": {
      "id": 1,
      "name": "Paxton",
      "description": "Paxton is the perfect place to find your dream career. With our easy-to-use platform, you can search for jobs based on your skills and experience. We also have a wide range of resources to help you prepare for your job search. So what are you waiting for? Start your job search today",
      "slogan": "Find your perfect career with Paxton.",
      "activitySectorId": 1,
      "headQuartersId": 2,
      "companySize": "BETWEEN_1_5",
      "foundedAt": "2022-10-01",
      "webSite": "...",
      "specializations": [
        "IT_and_Software",
        "AI",
        "Software_Development",
        "Software_Product_Design",
        "Project_Management"
      ],
      "locations": [2, 3],
      "photography": "...."
    }
  },
  "operationName": "CreateOrUpdateOrganization"
}

Please note you did not provide the schema definition of Specialization type, so I assume it contains a String, but you may need to modify.

[robertionut95b]

Hello @congotej,

I forgot to specify how Specialization looks like, but it is a simple Enum:

enum Specialization {
    Banking,
    Retail_banking,
    Corporate_and_Investment_Banking,
    Private_Banking,
    Financial_services,
...
}

I fail to see what is the issue with the JSON request. Both specialization and location fields are correctly built as Long and Enum arrays:

{
"specializations":["IT_and_Software","AI","Software_Development","Software_Product_Design","Project_Management"],
"locations":[2,3]
}

This kind of behaviour worked out-of-the box with graphql-kickstart, which I used prior to this.