wp-phpstan

PHPStan reports false positives in WordPress plugin code due to dynamic runtime behavior and WordPress-specific APIs. Applying WordPress-specific configuration and accurate PHPDoc typing patterns resolves these misleading static analysis errors.

To configure PHPStan for a WordPress theme, set up phpstan.neon using Composer-based entrypoints, validate WordPress stub availability, and scope analysis to first-party code. Add narrow ignoreErrors and stubs for third-party integrations instead of blanket baselining.

The best way to fix PHPStan errors for WordPress REST API requests and hook callbacks is by adding accurate PHPDoc typing patterns. This provides static analysis with exact type expectations for dynamic WordPress core functions.

You can use PHPStan with WooCommerce or ACF optional dependencies by managing third-party class discovery. Prefer adding stubs for these APIs and only use targeted ignore patterns when the dependencies are truly unavailable.

You should avoid blanket baseline workflows when setting up PHPStan in a WordPress project. Instead, update the phpstan configuration with narrow ignoreErrors and added stubs to properly resolve false positives and missing-type issues.

To type Action Scheduler argument arrays for PHPStan in WooCommerce, apply WordPress-specific PHPDoc typing patterns. This guides static analysis by defining the exact data shapes expected by scheduled action hooks.