Best Practices Analyzers

19 analyzers ensuring you follow Laravel ecosystem best practices and framework conventions.

Overview

Best Practices analyzers focus on Laravel-specific patterns, framework conventions, and architectural best practices. These analyzers help ensure your code follows Laravel's intended usage patterns and prevents common mistakes that can lead to maintainability issues or performance problems.

Key Analyzers

Laravel Conventions

Logic in Routes

Detects business logic in route files

High

Logic in Blade

Detects complex logic in Blade templates

High

Hardcoded Configuration

Detects configuration values outside config files

High

Pro Policy Authorization

Validates that resource controllers have corresponding Policy classes for proper authorization enforcement

High

Views & Frontend

Pro Accessibility

Validates that Blade templates follow basic accessibility best practices for inclusive web applications

Medium

Eloquent & Database

Eloquent N+1 Query

Detects N+1 query problems

High

Missing Chunk

Detects missing chunk() calls for large datasets

High

Missing Database Transactions

Detects operations that should use database transactions

High

Mixed Query Builder and Eloquent

Detects inconsistent query building patterns

High

Code Organization

Fat Model

Detects models with too much business logic that violate Single Responsibility Principle

Medium

Service Container Resolution

Detects manual service container resolution and recommends constructor dependency injection

High

Pro Middleware Misuse

Detects business logic in middleware that should be in controllers or services for proper separation of concerns

Medium

Error Handling & Logging

Silent Failure

Detects empty catch blocks and error suppression that hide failures

High

Missing Error Tracking

Ensures error tracking is configured

Info

Package Configuration

Pro Pennant Configuration

Validates Laravel Pennant feature flag configuration, driver settings, and usage patterns

Medium

Anti-Patterns

Helper Function Abuse

Detects overuse of global helper functions

Medium

Hardcoded Storage Paths

Detects hardcoded file paths

Medium

PHP-Side Data Filtering

Detects filtering that should be done in database

High

Framework Override

Detects dangerous extensions of Laravel core classes that break during framework upgrades

High

How They Work

Best Practices analyzers use:

1. Pattern Matching: Identifies Laravel-specific patterns and conventions
2. AST Analysis: Analyzes code structure to detect architectural violations
3. Query Analysis: Examines database queries for optimization opportunities
4. Convention Validation: Checks code against Laravel best practices

Running Best Practices Analyzers

Run All Best Practices Analyzers

php artisan shield:analyze --category=best-practices

Run Specific Analyzer

php artisan shield:analyze --analyzer=eloquent-n-plus-one
php artisan shield:analyze --analyzer=missing-database-transactions
php artisan shield:analyze --analyzer=fat-model

Run Multiple Analyzers

php artisan shield:analyze --analyzer=eloquent-n-plus-one,missing-database-transactions,chunk-missing

Best Practices

Development

• Run best practices analyzers during code reviews
• Fix High severity issues before merging
• Use analyzers to learn Laravel conventions

Code Reviews

• Review best practices violations in pull requests
• Use violations as teaching opportunities
• Ensure new code follows Laravel patterns

Team Standards

• Agree on which best practices are mandatory
• Document team-specific conventions
• Use analyzers to maintain consistency across codebase

Related Categories

• Security Analyzers - Prevent security vulnerabilities
• Code Quality Analyzers - Maintain code quality standards
• Reliability Analyzers - Prevent runtime errors
• Performance Analyzers - Optimize application performance