💬 suggestion: IMO, mentioning GraphQL extensions can be a bit confusing here because it requires to be aware of this concept of the GraphQL spec, and it could easily be misunderstood with the extension concept we have at SDK level.

I think we could:

• Not mention it at all, "Error code"
• Not mention GraphQL extension, "Error code (used by some providers)"

‏

Sounds good ! I would prefer the second one as it is not always present. (to inform customers why it's not there)

@rgaignault Question.

What does this path mean? Is it ok that it is an array of either strings or numbers? Are you sure everything is correct here?

Asking because for Android our json parser generator fails to process this and I want to know if I need to fix it (add support of oneOf(primitive types)).

Hey @aleksandr-gringauz ! Based on the spec, that's what I have : https://github.com/graphql/graphql-spec/blob/main/spec/Section%207%20--%20Response.md.

The value for a response path must be a list of path segments. Path segments that represent field response name must be strings, and path segments that represent list indices must be 0-indexed integers.

Also based on the examples it's either integer or string. Do you see an other way of declaring this ?

Thanks for the reply @rgaignault!

Do you see an other way of declaring this ?

For me the following option will work. Checked it in dd-sdk-android.

"path": {
  "type": "array",
  "description": "Path to the field that caused the error",
  "items": {
    "oneOf": [
      {
        "type": "object",
        "title": "String",
        "required": ["segment"],
        "properties": {
          "segment": {
            "type": "string"
          }
        }
      },
      {
        "type": "object",
        "title": "Integer",
        "required": ["segment"],
        "properties": {
          "segment": {
            "type": "integer"
          }
        }
      }
    ]
  },
  "readOnly": true
}

The problem with Kotlin is that we don't have String | Integer like typescript. We only have sealed classes, for example:

sealed interface Path {
    data class String(val segment: String): Path
    data class Integer(val segment: Int): Path
}

If I were to try to implement String | Integer I would have to generate something like:

sealed interface StringOrInt {
    data class String(val segment: String): StringOrInt
    data class Integer(val segment: Int): StringOrInt
}

And if oneOf(string|int) occurs multiple times in the schema, I would have to make different StringOrInt for them or somehow reuse a common one.

It all requires some work on the generator which I would like to avoid if possible.

Discussed with @maxep about how they do on iOS. I might implement similar solution on Android, but need more time to think.

For now, no action is needed from your side. Thanks!