graphql-backend

To standardize Laravel Lighthouse GraphQL conventions, organize schemas under backend/graphql and place resolvers in App\GraphQL\Queries and App\GraphQL\Mutations as invokable classes. This ensures clear folder structure and consistent naming conventions across your backend.

For Laravel Lighthouse GraphQL authentication, use standard directives like @guard and @auth to enforce consistent access control. Apply @globalId and @rename to maintain uniform schema field handling and ensure reliable directive usage across your backend.

To sync a backend GraphQL schema with the frontend client, run the documented schema dump commands after making backend edits. This workflow dumps the Laravel Lighthouse schema to the frontend and refreshes the client to ensure frontend-schema synchronization.

This GraphQL backend convention guide requires no additional dependencies. It provides standardization guidelines for projects already using Laravel Lighthouse, focusing on schema organization, directive usage, and resolver placement without needing external packages.

You should document fields in a Laravel Lighthouse GraphQL schema whenever you define or modify them in backend/graphql. The conventions enforce field documentation to maintain clear API contracts and ensure frontend-schema synchronization after dumping.