Download the PHP package arts/wp-plugin-standards without Composer

On this page you can find all versions of the php package arts/wp-plugin-standards. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of arts/wp-plugin-standards

Informations about the package wp-plugin-standards

arts/wp-plugin-standards

Shared PHP quality tooling for Arts WordPress plugins: the ArtsFramework PHPCS ruleset (WordPress-Core + PHPCompatibilityWP with a few deliberate exclusions) and a PHPStan base config (level max, WordPress-aware).

Before this package existed, every repo carried its own copy-pasted phpcs.xml — ~30 of them, already drifting (some named ArtsFramework, some ArtsBase). This is the single source of truth.

Install

Composer will ask to allow two plugins — both are required:

The first registers the ArtsFramework PHPCS standard; the second auto-registers the szepeviktor/phpstan-wordpress extension with PHPStan.

Use — PHPCS

phpcs.xml in your repo:

Then vendor/bin/phpcs / vendor/bin/phpcbf.

The ruleset sets testVersion 8.0- (PHP cross-version sniffs via PHPCompatibilityWP) and minimum_supported_wp_version 6.0. Override either in your own ruleset with a <config> element if a plugin needs different floors.

Use — PHPStan

phpstan.neon in your repo:

The base pins level max, PHP 8.0, and treatPhpDocTypesAsCertain: false (see the comment in phpstan/base.neon for why). Paths, bootstrap/stub files, and any ignoreErrors stay per-repo.

What's deliberately excluded from WordPress-Core

Generic.Arrays.DisallowShortArraySyntax, WordPress.Files.FileName, WordPress.PHP.YodaConditions, WordPress.NamingConventions.ValidHookName.UseUnderscores, and Universal.NamingConventions.NoReservedKeywordParameterNames — long-standing Arts house style, inherited from the original per-repo rulesets.

All versions of wp-plugin-standards with dependencies

PHP Build Version
Package Version
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package arts/wp-plugin-standards contains the following files

Loading the files please wait ...