issue: Cannot return null for non-nullable field Item.name

[notaphplover]

Where are you having the issue

• GraphQL
• JSON API

Is the issue affecting one of the two elements below ?

• Translations
• Definitions Files (Open API, GraphQL Schema, etc)

Description

When calling the API, a server error is thrown when Item.name is null.

Just send the following query:

{
  set(id: "dp5") @locale(lang: "en") {
    id,
    name,
    cards {
      abilities { effect, name, type },
      attacks { cost, damage, effect },
      category,
      effect,
      energyType,
      evolveFrom,
      hp,
      id,
      image,
      item { name },
      legal { expanded, standard },
      level,
      name,
      rarity,
      regulationMark,
      resistances { type, value },
      retreat,
      stage,
      suffix,
      trainerType,
      types,
      variants { firstEdition, holo, normal, reverse, wPromo },
      weaknesses { type, value }
    }
  }
}

Expected behavior

API serves a set.

Current behavior

API fails with the folowing payload:

{
  "errors": [
    {
      "message": "Cannot return null for non-nullable field Item.name.",
      "locations": [
        {
          "line": 20,
          "column": 14
        }
      ],
      "path": [
        "set",
        "cards",
        3,
        "item",
        "name"
      ]
    }
  ]
}

Context

https://www.apollographql.com/blog/using-nullability-in-graphql#what-happens-if-you-try-to-return-null-for-a-non-null-field

[mike7user]

I'm just finding this project, but your best option is to adjust the call to the field Item.name so if it holds a NULL value or an empty value to return an exception sp the system is comfortable with move past those instances without thinking it's an problem. I would avoid adding print statements for the exception because these instances of null or empty will happen a lot throughout the Pokémon tcg database. You have to run a test to see if it holds valid output. and adjust as needed. What file is it calling to and at what line? That's where you should add the exception. Then submit your findings.