graphql-query-pattern

Standardize AniList GraphQL queries by defining Retrofit @GraphQuery methods, placing operations in assets/graphql, and executing via GraphQLController to persist mapped entities in Room. This controller pattern handles validation, mapping, and threading centrally to ensure consistent data flows.

Handle GraphQL errors by validating GraphQLResponse within GraphQLController, extracting non-null data, and converting GraphQL errors into RequestError. This prevents manual unwrapping in data sources and safely propagates errors through DataState domain flows.

Pass variables to GraphQL mutations by assembling QueryContainerBuilder variables via IGraphPayload.toMap. This keeps operation name resolution synchronized with Retrofit tags and asset-backed .graphql queries for reliable remote source bindings.

GraphQLController manages threading centrally and persists mapped remote-to-local models into Room after validating the GraphQLResponse. It prevents manual unwrapping in data sources and emits final domain models through DataState.

No, you should not manually unwrap Response<GraphQLResponse<*>> in data sources. The GraphQLController pattern requires centralized validation of non-null data and safe error extraction to prevent fragile, one-off GraphQL handling.

Place .graphql files under the assets/graphql directory to synchronize them with Retrofit @GraphQuery interface methods. This asset-backed approach ensures operation name resolution and QueryContainerBuilder variables are correctly bound.