Coding Standards Laravel Package

Product Decisions This Supports

• Build vs Buy: Eliminates the need to develop and maintain custom PHPCS rules from scratch, saving engineering resources and ensuring alignment with TYPO3 v12+ best practices (now fully synchronized with TYPO3 Core). The updated package includes Symfony v7 support and PHP 8.3 compatibility, reducing friction for modern TYPO3 ecosystems.
• Roadmap Alignment: Enables long-term maintainability with:
  • Strict PHP 8.1+ and PHPUnit 10+ enforcement, aligning with TYPO3’s evolving stack.
  • Deprecation of legacy Symfony 4/5 support, pushing teams toward modern dependencies.
  • New CS rules and PHP-CS-Fixer optimizations, reducing false positives and improving CI efficiency.
• Use Cases:
  • TYPO3 extension development (now with Symfony v7 component support).
  • Large-scale TYPO3 applications leveraging PHP 8.3+ for performance gains.
  • Open-source TYPO3 projects requiring consistent contributor onboarding (e.g., via Code of Conduct integration and nightly CI support).
  • Teams migrating from older TYPO3 versions (v10/v11) to v12+, benefiting from automated core-standard synchronization.

When to Consider This Package

• Adopt when:
  • Working on TYPO3 v11+ projects (extensions or applications), especially those using Symfony v7 components or PHP 8.1+.
  • Using PHP_CodeSniffer in CI/CD and needing zero-configuration TYPO3-standard compliance.
  • Requiring cross-team consistency (e.g., distributed contributors, open-source projects) with automated style enforcement.
  • Prioritizing reduced technical debt via modern PHP/PHPUnit dependencies (e.g., PHP 8.3, PHPUnit 10).
• Look elsewhere if:
  • The project is not TYPO3-based (e.g., Laravel, Symfony standalone).
  • You need static analysis beyond style checks (e.g., PHPStan for logic errors)—though this package now includes updated PHPStan integration.
  • Using Symfony <v6 or PHP <8.1, as support for these is deprecated.
  • Custom coding standards conflict with TYPO3’s rules (e.g., legacy projects with non-standard formatting).

How to Pitch It (Stakeholders)

• Executives:

  "This updated package future-proofs our TYPO3 codebase by enforcing TYPO3 v12+ standards with zero engineering overhead. It reduces review cycles by 30%+ (via automated style checks) and lowers maintenance costs by aligning with modern PHP/Symfony dependencies. With PHP 8.3 and Symfony v7 support, we can accelerate feature delivery while ensuring long-term compatibility with TYPO3’s roadmap. Teams will spend less time debating formatting and more time innovating."

• Engineering:

  *"Upgrade to v0.8.0 for:

  • Seamless TYPO3 v12+ compliance (auto-syncs with Core standards).
  • Symfony v7 and PHP 8.3 support—no more legacy dependency conflicts.
  • Faster CI runs (optimized PHP-CS-Fixer rules and nightly build support).
  • One command to enforce standards:

    vendor/bin/phpcs --standard=vendor/typo3/coding-standards
    

  Deprecation note: Symfony 4/5 and PHP <8.1 are no longer supported—plan migrations if affected. The package now includes a Code of Conduct and strict coverage metadata for open-source projects."*