Coding Standard Laravel Package

Product Decisions This Supports

• Modernization of Tooling Stack: Aligns with roadmap items to upgrade legacy dependencies (e.g., doctrine/coding-standard to v8.1) and ensure compatibility with Composer 2, reducing technical debt and future-proofing the codebase.
• Build vs. Buy: Reinforces the decision to adopt this package over custom solutions by demonstrating active (if incremental) maintenance and alignment with modern PHP ecosystems.
• Developer Experience (DX) Initiatives: Supports CI/CD integration with updated tooling, ensuring seamless adoption of newer PHP standards (e.g., PSR-12 compatibility improvements in Doctrine v8.x) without disrupting workflows.
• Onboarding Acceleration: Leverages updated standards to maintain consistency as the team scales, especially with newer engineers familiar with Composer 2 and modern PHP tooling.
• Compliance with Team Standards: Provides a lightweight, maintained ruleset that evolves with PHP best practices, reducing the need for manual overrides or forks.

When to Consider This Package

• Adopt if:

  • Your team uses Doctrine v8.x or plans to upgrade from older versions (this release drops support for v6.x).
  • You’ve migrated to Composer 2 or are preparing to do so—this package now explicitly supports it.
  • You need minimal maintenance overhead but want to stay aligned with modern PHP standards (e.g., PSR-12 improvements in Doctrine v8.x).
  • Your CI/CD pipeline supports PHP_CodeSniffer or similar tools, and you’re ready to upgrade dependencies.
  • You prioritize long-term compatibility with Laravel’s evolving ecosystem (Doctrine is a core dependency for Laravel’s ORM).

• Look Elsewhere if:

  • You’re stuck on Composer 1 or have legacy constraints preventing upgrades (this release is Composer 2-only).
  • Your project relies on Doctrine v6.x or earlier (this release requires v8.1+).
  • You need custom rules beyond Doctrine’s scope—consider supplementing with php-cs-fixer or forking the package.
  • Your team requires active, frequent updates (last major update was 2020; while this is a dependency upgrade, the package itself isn’t actively maintained).
  • You’re not using Doctrine/Laravel heavily—this ruleset is optimized for those ecosystems.

How to Pitch It (Stakeholders)

For Executives: "We’ve updated our coding standards package to Doctrine v8.1, which includes critical upgrades like Composer 2 support and modern PHP alignment. This ensures our tooling stays current with Laravel’s ecosystem, reducing future migration risks. It’s a low-effort way to future-proof our codebase while maintaining consistency—think of it as a ‘free’ upgrade to keep pace with PHP best practices. The MIT license keeps us flexible, and the Composer 2 compatibility aligns with our long-term tech stack."

For Engineering: *"We’re upgrading the Doctrine coding standard to v8.1 in this package, which:

• Drops Composer 1 support (aligns with our Composer 2 migration).
• Improves PSR-12 compatibility (better for modern Laravel projects).
• Future-proofs our linting rules against breaking changes in newer PHP/Doctrine versions. Action items:

1. Audit our CI pipeline for Composer 1 dependencies that might conflict.
2. Test the upgrade in a staging repo to validate no false positives/negatives.
3. Document the change for the team—this is a breaking change for Composer 1 users. Prototype plan: Let’s test this in [Repo Y] first to catch edge cases before rolling it out."*

For Developers: *"Our code style tooling just got a minor but important upgrade—we’re now using Doctrine v8.1, which:

• Works with Composer 2 (so if you’re on Composer 1, you’ll need to upgrade soon).
• Fixes some edge cases with Laravel/Doctrine conventions.
• Keeps our linting rules modern and compatible with newer PHP versions. What changes for you:
• Your IDE/linter might flag new or adjusted rules (e.g., stricter PSR-12 checks).
• If you’re on Composer 1, you’ll need to upgrade to avoid conflicts. Let’s test it in [Repo Y]—try it out and report any issues so we can tweak the rules before full rollout."