README

Shared PHPStan Level 10 ruleset and Laravel Pint configuration for EaglePHP ecosystem projects.

Installation

composer require --dev demirkartal/eaglephp-code-quality

Enable the extension installer plugin in your project composer.json:

{
  "config": {
    "allow-plugins": {
      "phpstan/extension-installer": true
    }
  }
}

The installer is a transitive dependency of this package; allow-plugins must be set in the consumer project.

Usage

PHPStan

After installation, phpstan/extension-installer registers this package and all bundled extensions automatically. Your project root phpstan.neon should only define paths, optional baseline, and project-specific overrides:

• Do not manually include vendor/demirkartal/eaglephp-code-quality/phpstan.neon — the extension installer loads the base ruleset.
• Do not set customRulesetUsed: true in the consumer — it is declared in this package's phpstan.neon.
• With customRulesetUsed: true, built-in level rules are loaded via config.level10.neon in this package; setting only parameters.level in a consumer config does not register those rules.

# phpstan.neon (consumer project)
includes:
  - phpstan-baseline.neon

parameters:
  paths:
    - src
    - tests

./vendor/bin/phpstan analyse

PHPStan next (PHP 8.5 target)

Optional forward-compat check against phpVersion: 80500. Include your project phpstan.neon (paths/baseline) plus the vendor next profile — phpstan-next.neon only overrides phpVersion, so the base ruleset is not loaded twice:

# phpstan.next.neon (consumer project)
includes:
  - phpstan.neon
  - vendor/demirkartal/eaglephp-code-quality/phpstan-next.neon

./vendor/bin/phpstan analyse -c phpstan.next.neon

Laravel Pint

Pint is not auto-wired; pass the shared config explicitly:

./vendor/bin/pint --config vendor/demirkartal/eaglephp-code-quality/pint.json

Preset and standards

pint.json uses preset: per — PHP Evolving Recommendation (PER-CS), which builds on PSR-12 and PSR-1. A separate psr12 preset is not needed.

Explicit rules extend PER with:

• Strict types — declare_strict_types, void_return, import ordering
• PHPDoc (PHPStan Level 10 aligned) — native types preferred; when PHPDoc remains, use modern notation (array<T>, list<T>), remove deprecated tags (@access, @package), enforce param order and summary punctuation
• Layout — trailing commas, blank lines before statements, class attribute separation

Rules not enabled (conflict with native-type / PHPStan policy): phpdoc_add_missing_param_annotation, phpdoc_to_param_type, phpdoc_to_return_type.

After composer update, run composer format in consumer repos — PHPDoc diffs (T[] → array<T> / list<T>) are expected.

Example composer.json scripts:

{
  "scripts": {
    "format": "pint --config vendor/demirkartal/eaglephp-code-quality/pint.json",
    "format:check": "pint --config vendor/demirkartal/eaglephp-code-quality/pint.json --test",
    "phpstan": "phpstan analyse --memory-limit=512M"
  }
}

Features

• PHPStan Level 10 — strict static analysis for PHP ^8.4 || ^8.5 (lowest target: 80400).
• 100% type coverage — native types enforced for constants, properties, parameters, and return types.
• Type Perfect rules — disallows empty() / isset() on objects and parameter type removal in child classes.
• Auto-wired PHPStan extensions — via phpstan/extension-installer on composer install.
• Unified Pint profile — per preset (PER > PSR-12), modern PHPDoc types, strict imports

Core stack

Active config: phpstan.neon — bleedingEdge, config.level10.neon, phpVersion: 80400.

Alignment with PHPStan “Want to go further?”

This package implements the PHPStan “Want to go further?” recommendations out of the box:

Consumers do not need to duplicate vendor includes, customRulesetUsed, or parameters.level in their own phpstan.neon.

PHPStan rule levels

Levels are cumulative (level 6 includes 0–6).
Source: PHPStan Rule Levels (PHPStan 2.x → 0–10).

Level 10 does not replace level 9: it also treats missing types as mixed and forbids the same unsafe operations.

Extensions & rule packages

phpstan/extension-installer automatically loads and activates:

Strict analysis parameters

These flags extend beyond Level 10:

phpstan-strict-rules (via rules.neon, not duplicated in phpstan.neon) also enables: checkDynamicProperties, checkExplicitMixedMissingReturn, reportMaybesInMethodSignatures, reportMaybesInPropertyPhpDocTypes, reportWrongPhpDocTypeInVarTag, reportNonIntStringArrayKey (with bleeding edge), polluteScopeWithLoopInitialAssignments: false, and related scope-pollution guards.

Extending uncheckedExceptionClasses

Indexed NEON lists merge across included configs (append). Shared defaults (LogicException, RuntimeException) stay active when a consumer adds more entries — you do not need to re-list them. To replace the list entirely, use the NEON override suffix:

# Consumer phpstan.neon — add project-specific unchecked types (lists merge)
parameters:
  exceptions:
    uncheckedExceptionClasses:
      - 'Psr\Container\ContainerExceptionInterface'
      - 'Psr\Container\NotFoundExceptionInterface'

# Replace the entire list (drops shared LogicException / RuntimeException)
parameters:
  exceptions:
    uncheckedExceptionClasses!:
      - 'App\Infrastructure\InfraException'

This merge behaviour is guarded by composer analyse:unchecked-merge (tests/assert-unchecked-exception-merge.php).

missingCheckedExceptionInThrows does not require checkedExceptionClasses / checkedExceptionRegexes when using the unchecked-list mode (everything checked except listed classes). Those keys switch to the inverse model (only listed types are checked).

PHPStan does not require PHPDoc when native types suffice; missing type info is enforced at level 6+ and via type coverage.

License

MIT — see LICENSE.