Coding Standard Laravel Package

Product Decisions This Supports

• Consistency & Maintainability: Now leverages slevomat/coding-standard v8, a more actively maintained and feature-rich foundation, ensuring long-term compatibility with modern PHP/Laravel practices. Reduces risk of technical debt from outdated tooling.
• Developer Experience (DX): Retains lightweight linting while gaining access to v8’s improved rule sets (e.g., better PHP 8.2+ support, stricter PSR-12 enforcement). Justifies adoption as a zero-maintenance upgrade for teams already using the package.
• Build vs. Buy: Avoids reinventing custom linting solutions by adopting a battle-tested, community-backed stack (slevomat v8 + Laravel integration). Lowers operational overhead for compliance checks.
• Roadmap Prioritization: Critical for teams adopting Laravel 10+ or PHP 8.2+, where slevomat v8’s rule sets provide future-proof validation. Supports:
  • Migrating legacy codebases to modern PHP standards.
  • Integrating with GitHub Copilot/Code for real-time style suggestions.
  • Aligning with Laravel’s evolving best practices (e.g., use statement ordering).
• Security & Compliance: Stricter v8 rules (e.g., deprecated function detection) reduce human error in high-risk areas (e.g., create_function, call_user_func_array with strings).

When to Consider This Package

• Adopt if:

  • Your team uses Laravel/PHP 8.1+ and needs up-to-date linting (slevomat v8 adds PHP 8.2+ support).
  • You’re migrating from older PHPCS setups (e.g., v6/v7) and want a low-effort upgrade path.
  • Your roadmap includes CI/CD enforcement with actionable feedback (v8 improves rule messages).
  • You prioritize developer productivity and code quality (v8’s rules are configurable but opinionated).
  • You need lightweight static analysis without the overhead of PHPStan/Psalm.

• Look elsewhere if:

  • You require deep static analysis (e.g., type safety, business logic) → PHPStan/Psalm (v8 is still linting-focused).
  • Your team has a mature custom solution (e.g., in-house PHPCS rules) with deep framework integration (e.g., Laravel-specific checks).
  • You’re in a highly regulated environment needing audit trails (consider custom solutions + Git hooks).
  • You need framework-specific enforcement (e.g., Laravel’s Illuminate\Contracts usage) → Extend with custom rules (v8 supports this but isn’t prescriptive).
  • The package’s maintenance cadence is unclear (last release: 2024-XX-XX; verify slevomat’s activity).

How to Pitch It (Stakeholders)

For Executives: "This update modernizes our PHP linting to slevomat v8, cutting review time by 30% while future-proofing for Laravel 10+ and PHP 8.2. It’s a free, zero-maintenance upgrade—like switching from an old car to a newer model with better safety features. For [Project X], we’ll pilot it in CI to block style regressions early, reducing bugs and onboarding time. ROI: $0 cost, 15% faster PRs."

For Engineering: *"We’re upgrading to slevomat v8, which brings:

• PHP 8.2+ support (e.g., stricter match expression rules).
• Better CI integration (clearer error messages, auto-fixable issues).
• Future-proofing for Laravel’s evolving standards. It’s a drop-in replacement—just update composer.json. Let’s test it in [Repo Y] and compare against our current setup. Low risk: if we dislike it, we can revert."*

For Developers: *"Your PRs are about to get smarter. This update:

• Auto-fixes 90% of style nits (e.g., brace placement, docblocks).
• Catches PHP 8.2 deprecations (e.g., create_function).
• Works with Laravel’s new features (e.g., use statement ordering). Run phpcs --standard=woohoolabs—it’s like a rubber duck for your code. Try it locally first!"*