Php Coding Standard Laravel Package

Product Decisions This Supports

• Enforcing Consistency: Standardize code quality across Laravel/PHP projects, reducing onboarding friction for new developers and ensuring uniformity in legacy codebases.
• Developer Experience (DX): Automate repetitive code review tasks (e.g., PSR compliance, naming conventions) to free up engineering time for higher-value work.
• Build vs. Buy: Avoid reinventing a custom coding standard by leveraging a pre-configured, battle-tested solution (based on Symplify/EasyCodingStandard), reducing maintenance overhead.
• Roadmap Alignment: Critical for teams adopting Symfony/Laravel or WordPress, where adherence to framework-specific conventions (e.g., Symfony’s dependency injection, Laravel’s naming patterns) is non-negotiable.
• CI/CD Integration: Enable pre-commit hooks or GitHub Actions to block non-compliant code early, improving release velocity and reducing tech debt.

When to Consider This Package

• Adopt if:

  • Your team uses Laravel/Symfony/WordPress and lacks a standardized coding style.
  • You prioritize automated code quality but don’t want to manage a custom ECS config from scratch.
  • Your project has mixed PHP versions (e.g., legacy + modern) and needs flexible rule sets.
  • You’re open to MIT-licensed tools with minimal dependencies (only requires EasyCodingStandard).

• Look elsewhere if:

  • Your team already has a custom coding standard (e.g., PHP-CS-Fixer + custom rules) that’s deeply integrated into workflows.
  • You need enterprise-grade support (this package has low adoption; consider PHP-CS-Fixer or PSR-12 for broader compatibility).
  • Your project uses non-PHP frameworks (e.g., Node.js, Go) or has strict legacy constraints (e.g., PHP 5.x).
  • You require real-time IDE feedback (pair with PHPStorm inspections or VSCode extensions instead).

How to Pitch It (Stakeholders)

For Executives: "This package lets us enforce consistent, high-quality PHP code automatically—saving 10–15 hours/week in manual code reviews. By adopting whatwedo’s pre-configured rules (tailored for Laravel/Symfony/WordPress), we’ll reduce bugs, speed up onboarding, and align with industry best practices. It’s a low-lift way to future-proof our codebase for scaling."

For Engineering: *"This is a drop-in replacement for manual PSR checks. It runs via vendor/bin/ecs and integrates seamlessly with:

• CI/CD (block bad PRs early).
• Pre-commit hooks (fail fast locally).
• Custom configs (extend or override rules as needed). No flaky custom scripts—just Symplify/EasyCodingStandard with Whatwedo’s battle-tested tweaks. Let’s pilot it on [Project X] and measure review time savings."*

For Developers: *"Imagine your IDE flagging inconsistent code before you commit. This tool does that—and more:

• Fixes naming, spacing, and PSR issues in one command.
• Works out-of-the-box for Laravel/Symfony/WordPress.
• Configurable via ecs.php (e.g., skip tests, add custom rules). Start with composer require whatwedo/php-coding-standard and run vendor/bin/ecs check src/ --config=vendor/whatwedo/php-coding-standard/config/whatwedo-symfony.php."*