https://github.com/johnbillion/wp-compat
PHPStan extension to help verify that your plugin or theme remains compatible with its minimum supported version of WordPress
https://github.com/johnbillion/wp-compat
phpstan phpstan-extension wordpress
Last synced: 4 months ago
JSON representation
PHPStan extension to help verify that your plugin or theme remains compatible with its minimum supported version of WordPress
- Host: GitHub
- URL: https://github.com/johnbillion/wp-compat
- Owner: johnbillion
- License: mit
- Created: 2024-09-03T20:31:38.000Z (over 1 year ago)
- Default Branch: trunk
- Last Pushed: 2025-07-03T21:39:13.000Z (7 months ago)
- Last Synced: 2025-09-28T20:51:37.659Z (4 months ago)
- Topics: phpstan, phpstan-extension, wordpress
- Language: PHP
- Homepage:
- Size: 653 KB
- Stars: 22
- Watchers: 3
- Forks: 1
- Open Issues: 1
-
Metadata Files:
- Readme: readme.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
Awesome Lists containing this project
README
# WPCompat
WPCompat is a PHPStan extension which helps verify that your PHP code is compatible with a given version of WordPress. You can use it to help ensure that your plugin or theme remains compatible with its "Requires at least" version.
It works by checking that any WordPress functions, class methods, actions, or filters that are in use were introduced prior to the minimum version of WordPress that your code supports. For example, if your plugin or theme supports WordPress 6.0 or higher but the `get_template_hierarchy()` function is used unconditionally, the extension will trigger an error because that function was only introduced in WordPress 6.1.
If your code is correctly guarded with a valid `function_exists()` or `method_exists()` check then an error won't be triggered.
## Status
Version information was last updated for WordPress 6.8.
## Requirements
* PHPStan 2.0 or higher
* PHP 7.4 or higher (tested up to PHP 8.4)
## Installation
```shell
composer require --dev johnbillion/wp-compat
```
If you also install [phpstan/extension-installer](https://github.com/phpstan/extension-installer) then you're all set!
Manual installation
If you don't want to use `phpstan/extension-installer`, include extension.neon in your project's PHPStan config:
```neon
includes:
- vendor/johnbillion/wp-compat/extension.neon
```
## Configuration
### Themes
If your style.css file contains a "Requires at least" header then wp-compat will read this header and use its value as the minimum supported WordPress version. There is no need for any additional config.
### Plugins
If the name of your main plugin file matches its parent directory -- for example `my-plugin/my-plugin.php` -- then wp-compat will read the "Requires at least" header from this file and use its value as the minimum supported WordPress version. There is no need for any additional config.
If your main plugin file is named otherwise or located elsewhere, you can specify its name in your PHPStan config file:
```neon
parameters:
WPCompat:
pluginFile: my-plugin.php
```
### Manual config
Alternatively you can specify the minimum supported WordPress version number of your plugin or theme directly in your PHPStan config file. Note that this must be a string so it must be wrapped in quote marks.
```neon
parameters:
WPCompat:
requiresAtLeast: '6.0'
```
Any version number in `major.minor` or `major.minor.patch` format is accepted.
## Ignoring errors
You can ignore an error from this extension by using its error identifier. For full information, see [the PHPStan guide to ignoring errors](https://phpstan.org/user-guide/ignoring-errors).
### Functions and methods
If your code is correctly guarded with a valid `function_exists()` or `method_exists()` check then an error won't be triggered.
```php
// @phpstan-ignore WPCompat.functionNotAvailable
wp_foo();
// @phpstan-ignore WPCompat.methodNotAvailable
WP::foo();
```
### Actions and filters
There is no concept of checking the existence of an action or filter in WordPress in order to guard its usage. You can still ignore an error for an action or filter using its error identifier, which contains a sanitized version of the hook name.
```php
// @phpstan-ignore WPCompat.filterNotAvailable.filtername
add_filter( 'filter_name', 'callback' );
// @phpstan-ignore WPCompat.actionNotAvailable.myactionname
add_action( 'my_action_name', 'callback' );
```
## Technical details
This extension does not scan your project in order to detect the `@since` versions of WordPress functions, methods, and hooks. This information is included directly in the extension. This approach ensures that your code is always tested against the most up to date and most accurate `@since` documentation, regardless of the version of WordPress that your tests are using.
### Functions and methods
The [symbols.json](symbols.json) file contains a dictionary of all functions and methods in WordPress along with the version of WordPress in which they were introduced.
The file can be regenerated by running:
```shell
composer generate
```
The JSON schema for the file can be found in [schemas/symbols.json](schemas/symbols.json).
### Actions and filters
Information about actions and filters is provided by [the `wp-hooks/wordpress-core` package](https://github.com/wp-hooks/wordpress-core-hooks).
## Sponsors
The time that I spend maintaining this extension and others is in part sponsored by:
Plus all my kind sponsors on GitHub:
Click here to find out about supporting my open source tools and plugins.
## License
MIT