Issue
All the issues that can be collected while analyzing a graphql document
Types
A fragment has an @include or @skip directive. While this is valid GraphQL, the responseBased codegen does not support that
A deprecated field/enum is used
A grammar error
Certain enum value names such as type
are reserved for Apollo.
A variable is unused
When models are nested, upper case fields are not supported as Kotlin doesn't allow a property name with the same name as a nested class. If this happens, the easiest solution is to add an alias with a lower case first letter. If there are a lot of such fields, the Apollo compiler option flattenModels
can also be used to circumvent this error at the price of possible suffixes in model names.
A GraphqQL validation error as per the spec