-
Installing 1.0.0, I get the following error on PHP_CodeSniffer version 3.4.0.
```
Warning: require_once(/usr/local/bin/wpcs/WordPress/PHPCSAliases.php): failed to open stream: No such file or d…
-
## What problem would the enhancement address for VIP?
The [VariableAnalysis sniff](https://github.com/Automattic/VIP-Coding-Standards/blob/0363baf7ae0d92b2662bc0140da12709cbc7ee02/WordPressVIPMinimu…
-
VIPCS currently has PHPCS 3.2.3 as the minimum requirement.
[WPCS 2.0 will have PHPCS 3.3.1 as the minimum requirement](https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/pull…
-
I did a fresh install of the VIP standards using the following command from this handy [guide](https://wpvip.com/documentation/how-to-install-php-code-sniffer-for-wordpress-com-vip/):
`composer g req…
-
## What problem would the enhancement address for VIP?
Reduce the amount of noise and/or code comments clients add to reduce noise :)
## Describe the solution you'd like
Lets remove the code sn…
-
WPCS has a [ticket](https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/pull/1596) to remove the `PHPAliases.php` file that VIPCS currently references.
For WPCS 2.0, we'll need…
-
## Bug Description
[This commit](https://github.com/Automattic/VIP-Coding-Standards/commit/ae36ef4d44fe1369d7f7a00115e915f65cdda3bb) (see #58) added an exclusion for `WordPress.VIP.ValidatedSan…
-
## What problem would the enhancement address for VIP?
Now that VIPCS uses sniffs from WPCS 2.0, we can use the [IniSet](https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/blo…
-
There's a pending PR by @david-binda for the VIP standards at https://github.com/Automattic/VIP-Coding-Standards/pull/126 that tries to detect conflict resolution text in files, e.g.
```php
tomjn updated
5 years ago
-
When adding a `pre_option_*` filter, we should try to check if `get_current_blog_id()` is being referenced.
> Since the theme is being loaded even in non-standard situations (api, jobs system) you sh…