wp-phpstan

Fix PHPStan false positives in WordPress by adding WordPress-specific PHPDoc for REST requests, hook callbacks, database results, and filters, or by configuring targeted stub packages to resolve dynamic runtime APIs.

Configure phpstan.neon for a WordPress codebase by validating paths, exclusions, and ignoreErrors settings, ensuring WordPress stub packages are present and referenced, and generating baseline files to manage existing errors.

PHPStan reports unknown classes for WordPress hooks and REST APIs because these core APIs, hook callbacks, and request types are often resolved only at runtime rather than statically, requiring specific PHPDoc annotations to resolve.

The best way to use a PHPStan baseline for WordPress is as a temporary migration tool that tracks existing errors without masking new regressions, updating phpstan-baseline.neon while fixing errors with precise type corrections.

Add correct PHPStan types for Action Scheduler arguments by applying WordPress-specific phpstan-param annotations to define precise argument shapes, preferring type corrections over broad ignoreErrors patterns to ensure reliable static analysis.

Use ignoreErrors instead of stubs for missing WordPress classes only when the third-party dependency cannot be confirmed, applying narrow ignoreErrors patterns rather than broad exclusions to maintain strict type checking where possible.