laravel-best-practices

Fix N+1 queries in Laravel by eager loading relationships with the with() method before iterating. You can also enable Model::preventLazyLoading() in AppServiceProvider during development to throw exceptions when lazy loading occurs.

Laravel validation best practices recommend extracting rules into dedicated Form Request classes and always using validated() instead of request->all() for mass operations. Array notation for rules is preferred in new code, but match the project's existing convention.

Keep Laravel controllers thin, aiming for under ten lines per method, by extracting business logic into invokable action or service classes. Use constructor dependency injection and type-hint Form Requests for automatic validation.

The rules note that version-sensitive Laravel APIs should be verified against the installed version using documentation search or by inspecting the installed framework. The guidance prioritizes consistency with the existing codebase over any single rule.

Duplicate job execution happens when the queue retry_after configuration is shorter than the job's timeout, causing the worker to re-dispatch a still-running job. Set retry_after safely greater than the maximum job timeout and consider implementing ShouldBeUnique.

Use cache tags in Laravel when you need to invalidate related groups of entries atomically with a single flush call. Tags only work with redis, memcached, and dynamodb drivers, not the file or database cache stores.