graphql-operations

Best practices guide for writing efficient, type-safe GraphQL operations and organizing them with fragments. This guide covers best practices for writing GraphQL operations (queries, mutations, subscriptions) as a client developer. Well-written operations are efficient, type-safe, and maintainable. Detailed documentation for specific topics: - Covers queries, mutations, subscriptions, and fragments with naming conventions, variable syntax, and directive usage - Emphasizes core principles: request only needed fields, name all operations, use variables instead of hardcoded values, and include id fields for cacheability - Recommends colocating fragments with components and using @include / @skip directives for conditional field selection - Compatible with any GraphQL client (Apollo Client, urql, Relay) and includes reference documentation for queries, mutations, fragments, variables, and tooling - Queries - Query patterns and optimization - Mutations - Mutation patterns and error handling - Fragments - Fragment organization and reuse - Variables - Variable usage and types - Tooling - Code generation and linting - ALWAYS name your operations (no anonymous queries/mutations) - ALWAYS use variables for dynamic values - ALWAYS request only the fields you need - ALWAYS include id field for cacheable types - NEVER hardcode values in operations - NEVER duplicate field selections across...