-
-
### Current situation
The WordPress Coding Standards currently enforce file names to:
1. Be all lowercase;
2. Use hyphens instead of underscores as word separators;
3. Have a `class-` prefix for…
-
See: https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards
Note: depending on the volume of issues found we can either correct them as part of this issue or spin up a separate is…
-
**Is your feature request related to a problem? Please describe.**
Similar to the i18n sniffs in WPCS there could be some custom ESLint rules to catch some common i18n mistakes.
**Describe the s…
-
Just like `die()` or `exit()`, `throw` will send to the screen unless the Exception is caught.
Should we start checking throw statements for output escaping ?
```php
throw new Exception( "There…
-
Error:
> dtolnay/rust-toolchain@stable, dtolnay/rust-toolchain@1.54, and dtolnay/rust-toolchain@nightly are not allowed to be used in mozilla/cbindgen. Actions in this workflow must be: within a rep…
-
## Is your feature request related to a problem?
Suppose I have the following code:
```
$variable = 'foo';
$my_array["a_string_{$variable}"] = 'bar';
```
This res…
-
Running PHPCS with WPCS over code warns about code (or security) practices and of course makes repository compliant with WordPress coding rules/standards.
It is not that I especially like rules :g…
-
PHPCS 3.3.0 will change the way class based return type declarations are tokenized.
Previously, a class based return type was tokenized as:
* `ClassName` => `T_STRING`
* `NSName\NSSubName\ClassNa…
-
## Is your feature request related to a problem?
Should we maybe put all the scripts that are used for testing purposes (lint checks, cs checks, tests, check-complete, etc.) under one namespace (sa…