graphql-schema

This guide covers best practices for designing GraphQL schemas that are intuitive, performant, and maintainable. Schema design is primarily a server-side concern that directly impacts API usability. Best Practice: Use [Type!]! for lists - empty list over null, no null items. Detailed documentation for specific topics: - Think about what queries clients will write - Organize types around use cases, not database tables - Expose capabilities, not implementation details - Use clear, descriptive names - Make nullability intentional - Document with descriptions - Plan for backwards compatibility - Use deprecation before removal - Avoid breaking changes - Types - Type design patterns, interfaces, unions, and custom scalars - Naming - Naming conventions for types, fields, and arguments - Pagination - Connection pattern and cursor-based pagination - Errors - Error modeling and result types - Security - Security best practices for schema design - Define types based on domain concepts, not data storage - Use interfaces for shared fields across types - Use unions for mutually exclusive types - Keep types focused (single responsibility) - Avoid deep nesting - flatten when possible - Fields should be named from client's perspective - Return the most specific type possible - Make expensive fields explicit (consider arguments) - Use arguments for filtering, sorting, pagination - Use single...