Download the PHP package lumnd/plato-coding-standard without Composer

lumnd/plato-coding-standard

PHP_CodeSniffer rules for PlatoPHP projects. The standard starts from PSR-12, removes the naming and brace conventions PlatoPHP deliberately does not follow, then adds a project sniff that enforces the replacement rules instead of leaving both styles legal.

简体中文

Use it when a PHP project wants:

• A Composer-installable PHPCS standard that can be referenced as <rule ref="PlatoPHP"/>
• PSR-12 as the base style, with explicit PlatoPHP conventions layered on top
• Lowercase snake_case classes, functions, and methods enforced consistently
• Allman braces and one-space control parentheses checked and fixed by phpcbf
• Naming rules that report violations without attempting unsafe automatic renames

Excluding a PSR-12 sniff only makes both spellings legal. A tree that excludes Squiz.Classes.ValidClassName does not require snake_case — it stops having an opinion, and the two styles drift apart inside one repository with nothing to say so. This package is both halves: the exclusions, and ProjectConventionsSniff, which rejects the PSR-12 spelling in their place.

It exists because the exclusions were pasted into three repositories and drifted. One copy was missing Squiz.Functions.MultiLineFunctionDeclaration.NewlineBeforeOpenBrace and still errored on wrapped signatures; one carried a bug in the sniff that the others had already fixed; one shipped a standard named after the wrong project. A convention with three copies has no authority.

Requirements

Install

This package's type is phpcodesniffer-standard, which is what dealerdirect/phpcodesniffer-composer-installer scans installed packages for. It writes this directory into phpcs's installed_paths, and that is what lets a consumer name the standard instead of spelling out a path into vendor/. The plugin is a hard requirement rather than a suggestion: without it the standard installs but never registers, and the ruleset fails to resolve the name with an error that does not say why.

Composer will not run a plugin a project has not allowed, so the consuming composer.json needs:

Use

A consumer's phpcs.xml keeps what is genuinely its own — which directories to check, which generated output to skip — and refs the standard by name:

Everything else — the PSR-12 base, the exclusions, the 120 column soft limit, Allman braces for functions and closures, ignore_warnings_on_exit — comes with the name.

What it enforces

All codes are prefixed PlatoPHP.Style.ProjectConventions.

Zero errors is the gate. The 120 column limit is a warning, which PSR-12 requires it to be, and ignore_warnings_on_exit keeps it out of the exit code.

What phpcbf fixes, and what it will not

The whitespace rules are fixable — composer style:fix rewrites if($x){ into the convention, including moving else and catch onto their own lines. Two cases are reported without a fix on purpose, because closing the gap would change more than formatting:

• A condition wrapped over several lines. Turning the newline into a space would join two lines rather than insert one space.
• A comment between the signature and the brace. It belongs on one side of the break and the sniff does not know which.

The naming rules are never fixable. Renaming a method means finding its callers, which is not something a formatter should attempt.

Exceptions

Magic methods are exempt from both naming rules. __toString, __callStatic and __debugInfo are camelCase and __construct is public while starting with an underscore — the engine owns those spellings, so they are not a project's to choose. The sniff carries PHP's list and skips it.

A name a third party dictates is not relaxed, it is suppressed where it happens. A class implementing PSR-16 must provide getMultiple(); renaming it would mean not implementing the interface. Mark that class rather than widening the rule for everybody:

ProjectConventionsSniff does the same to itself: PHPCS's loader requires a StudlyCaps class name ending in Sniff, so the file carries a one-line phpcs:ignore for its own ClassName rule.

Tests

Runs the standard over tests/fixtures and asserts what fires, what does not, what phpcbf rewrites, that a second fix run changes nothing, and that the two unfixable cases come back byte-identical. There is no test framework: a coding standard is a dependency of everybody else's test setup, and giving it one of its own buys a version conflict for nothing.

Checks this package against the standard it ships.

License

MIT.