Juliette
Juliette
See the conversation here: https://github.com/WordPress/WordPress-Coding-Standards/pull/2334#discussion_r1294579815 Basically we'd need a little (bash or otherwise) script to gather the files in the `WordPress/Docs` directory and then run the following command against each...
The `ControlStructureSpacing` (after the removal of the function handling in #2328) is largely a copy of an upstream sniff (`Squiz.WhiteSpace.ControlStructureSpacing`) to allow for 1 space on the inside of parentheses...
## Is your feature request related to a problem? A sniff should be added to address the following handbook rule: > Aliases can be used to prevent name collisions (two...
## Is your feature request related to a problem? A sniff should be added to address the following handbook rule: > Namespace declarations should have exactly one blank line before...
## Is your feature request related to a problem? A sniff should be added to address the following handbook rule: > Each part of a namespace name should consist of...
The following snippet of code triggers the `WordPress.CSRF.NonceVerification` sniff. ```php if ( ! isset( $_POST['field'] ) ) { // Do something (not using the post variable). } ``` As this...
Placeholder issue for action in WPCS 4.0.0. - [ ] `WordPress.NamingConventions.ValidFunctionName` sniff: remove exceptions for PHP 4 constructor/destructor methods.
There are a number of lists in WPCS which should be updated on a regular basis - on every WP release - and gathering the information needed for this manually...
The "Helper" classes and traits are currently tested via the sniff (integration) tests. It would be preferable to have dedicated test for the Helper classes and traits though. In most...
## Bug Description According to the handbook: > Class, trait, interface and enum names should use capitalized words separated by underscores. Any acronyms should be all upper case. Ref: https://developer.wordpress.org/coding-standards/wordpress-coding-standards/php/#naming-conventions...