Extra strict and opinionated rules for PHPStan
PHPStan focuses on finding bugs in your code. But in PHP there's a lot of leeway in how stuff can be written. This repository contains additional rules that revolve around strictly and strongly typed code with no loose casting for those who want additional safety in extremely defensive programming:
- Require booleans in
elseif, ternary operator, after
!, and on both sides of
- Require numeric operands or arrays in
+and numeric operands in
- These functions contain a
$strictparameter for better type safety, it must be set to
array_keys(3rd parameter; only if the 2nd parameter
- Variables assigned in
whileloop condition and
forloop initial assignment cannot be used after the loop.
- Types in
casevalue must match. PHP compares them loosely by default and that can lead to unexpected results.
- Statically declared methods are called statically.
empty()- it's a very loose comparison (see manual), it's recommended to use more strict one.
- Always true
is_*functions and strict comparisons
!==. These checks can be turned off by setting
- Correct case for referenced and called function names.
- Correct case for inherited and implemented method names.
Additional rules are coming in subsequent releases!
To use these rules, require it in Composer:
composer require --dev phpstan/phpstan-strict-rules
And include rules.neon in your project's PHPStan config:
includes: - vendor/phpstan/phpstan-strict-rules/rules.neon
If you don't want to start using all the available strict rules at once but only one or two, you can! Just don't include the whole
rules.neon from this package in your configuration, but look at its contents and copy only the rules you want to your configuration:
- class: PHPStan\Rules\StrictCalls\StrictFunctionCallsRule tags: - phpstan.rules.rule - class: PHPStan\Rules\SwitchConditions\MatchingTypeInSwitchCaseConditionRule tags: - phpstan.rules.rule