-
Notifications
You must be signed in to change notification settings - Fork 60
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'trunk' into add/cli-tests
- Loading branch information
Showing
57 changed files
with
1,197 additions
and
64 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,66 @@ | ||
# Plugin Check | ||
|
||
A repository for the new Plugin Check plugin from the [WordPress Performance Team](https://make.wordpress.org/performance/). | ||
This repository is for the WordPress plugin checker, a tool for plugin developers to analyze their plugin code and flag any violations or concerns around plugin development best practices, from basic requirements like correct usage of internationalization functions to accessibility, performance, and security best practices. | ||
|
||
If you would like to contribute please see the [CONTRIBUTING.md guide here](/CONTRIBUTING.md). | ||
The WordPress plugin checker was [first proposed in summer 2022](https://make.wordpress.org/plugins/2022/07/05/proposal-for-a-wordpress-plugin-checker/) and is now at an early MVP stage. | ||
|
||
## Features | ||
|
||
### For end users | ||
|
||
* Allows analyzing any installed plugin using either a WP Admin screen or a WP-CLI command. | ||
* Supports two kinds of checks: | ||
* Static checks, which analyze the code, either using PHPCodeSniffer sniffs or custom logic e.g. using regular expressions. | ||
* Runtime checks, which actually execute certain parts of the code, such as running specific WordPress hooks with the plugin active. | ||
* Allows customizing which checks are run, either via a list of individual check identifiers, or specific check categories. | ||
* Comes with an ever-growing list of checks for various plugin development requirements and best practices. Please see the [`Abstract_Check_Runner::register_checks()` method](/includes/Checker/Abstract_Check_Runner.php#L358) for a quick overview of currently available checks. | ||
|
||
### For developers | ||
|
||
* Facilitates efficient yet flexible authoring of new checks, either using a base class for common check patterns, or implementing an interface for more specific checks. | ||
* Every check has to implement either the [`Static_Check`](/includes/Checker/Static_Check.php) or the [`Runtime_Check`](/includes/Checker/Runtime_Check.php) interface. | ||
* Most checks will benefit from extending either the [`Abstract_File_Check`](/includes/Checker/Checks/Abstract_File_Check.php), the [`Abstract_PHPCodeSniffer_Check`](/includes/Checker/Checks/Abstract_PHP_CodeSniffer_Check.php), or the [`Abstract_Runtime_Check`](/includes/Checker/Checks/Abstract_Runtime_Check.php) class. | ||
* Comes with comprehensive unit test coverage. | ||
|
||
## How to use | ||
|
||
The WordPress plugin checker is a WordPress plugin itself, which can be installed on any WordPress site. While it is implemented in a way that should avoid any disruptions on the site that it is being used on, it is still **advised not to use the plugin checker in a production environment**. | ||
|
||
Currently, the only way to install the plugin checker is to download it from this GitHub repository. Please see the [contributing section below](#contributing) for further instructions. Once a first beta version is available, it will be distributed in a standalone ZIP file, e.g. via the wordpress.org plugin repository. | ||
|
||
After having the plugin activated, you can analyze any other plugin installed on the same site, either using the WP Admin user interface or WP-CLI: | ||
|
||
* To check a plugin using WP Admin, please navigate to the _Tools > Plugin Check_ menu. You need to be able to manage plugins on your site in order to access that screen. | ||
* To check a plugin using WP-CLI, please use the `wp plugin check` command. For example, to check the "Hello Dolly" plugin: `wp plugin check hello.php` | ||
* Note that by default when using WP-CLI, only static checks can be executed. In order to also include runtime checks, a workaround is currently necessary using the `--require` argument of WP-CLI, to manually load the `cli.php` file within the plugin checker directory before WordPress is loaded. For example: `wp plugin check hello.php --require=./wp-content/plugins/plugin-check/cli.php` | ||
|
||
## Contributing | ||
|
||
To set up the repository locally, you will need to clone this GitHub repository (or a fork of it) and then install the relevant dependencies: | ||
|
||
``` | ||
git clone https://github.com/10up/plugin-check.git wp-content/plugins/plugin-check | ||
cd wp-content/plugins/plugin-check | ||
composer install | ||
npm install | ||
``` | ||
|
||
### Built-in development environment (optional) | ||
|
||
With the above commands, you can use the plugin in any development environment as you like. The recommended way is to use the built-in development environment, which is based on the [`@wordpress/env` package](https://www.npmjs.com/package/@wordpress/env), as that will allow you to use the preconfigured commands to e.g. run unit tests, linting etc. You will need to have Docker installed to use this environment. | ||
|
||
You can start the built-in environment as follows: | ||
``` | ||
npm run wp-env start | ||
``` | ||
|
||
If you want to stop the environment again, you can use: | ||
``` | ||
npm run wp-env stop | ||
``` | ||
|
||
For further information on contributing, please see the [contributing guide](/CONTRIBUTING.md). | ||
|
||
## License | ||
|
||
The WordPress plugin checker is free software, and is released under the terms of the GNU General Public License version 2 or (at your option) any later version. See [LICENSE](/LICENSE) for complete license. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,73 @@ | ||
<?php | ||
/** | ||
* Class WordPress\Plugin_Check\Checker\Check_Categories | ||
* | ||
* @package plugin-check | ||
*/ | ||
|
||
namespace WordPress\Plugin_Check\Checker; | ||
|
||
/** | ||
* Abstract Check Runner class. | ||
* | ||
* @since n.e.x.t | ||
*/ | ||
class Check_Categories { | ||
|
||
// Constants for available categories. | ||
const CATEGORY_GENERAL = 'general'; | ||
const CATEGORY_PLUGIN_REPO = 'plugin_repo'; | ||
const CATEGORY_SECURITY = 'security'; | ||
const CATEGORY_PERFORMANCE = 'performance'; | ||
const CATEGORY_ACCESSIBILITY = 'accessibility'; | ||
|
||
/** | ||
* Returns an array of available categories. | ||
* | ||
* @since n.e.x.t | ||
* | ||
* @return array An array of available categories. | ||
*/ | ||
public static function get_categories() { | ||
static $categories = ''; | ||
if ( ! $categories ) { | ||
$constants = ( new \ReflectionClass( __CLASS__ ) )->getConstants(); | ||
|
||
/** | ||
* List of categories. | ||
* | ||
* @var string[] $categories | ||
*/ | ||
$categories = array_values( | ||
array_filter( | ||
$constants, | ||
static function( $key ) { | ||
return strpos( $key, 'CATEGORY_' ) === 0; | ||
}, | ||
ARRAY_FILTER_USE_KEY | ||
) | ||
); | ||
} | ||
|
||
return $categories; | ||
} | ||
|
||
/** | ||
* Returns an array of checks. | ||
* | ||
* @since n.e.x.t | ||
* | ||
* @param array $checks An array of Check instances. | ||
* @param array $categories An array of categories to filter by. | ||
* @return array Filtered $checks list. | ||
*/ | ||
public static function filter_checks_by_categories( array $checks, array $categories ) { | ||
return array_filter( | ||
$checks, | ||
static function( $check ) use ( $categories ) { | ||
// Return true if at least one of the check categories is among the filter categories. | ||
return (bool) array_intersect( $check->get_categories(), $categories ); | ||
} | ||
); | ||
} | ||
} |
Oops, something went wrong.