This is a ground-up rewrite of the Acquia PHP standard to be based on PSR-12 and compatible with Drupal standards. In other words, any code adhering to Acquia PHP will also adhere to Drupal standards, but not necessarily vice-versa.
This means that Acquia PHP is a stricter subset of PSR-12 and the Drupal standards, which is a paradigm shift from its original implementation as a looser standard (and hence, base of) the Drupal standards. This warrants a new major release.
PER isn't available in PHPCS yet, but the good news is it's mostly backwards-compatible (i.e., only contains additions for new PHP features) and can we can basically swap it in for PSR-12 when it lands:
https://github.com/PHPCSStandards/PHP_CodeSniffer/issues/29
The best way to test this is against projects already on the latest version of the AcquiaPHP or AcquiaDrupal* standards.
For AcquiaDrupal* projects, see that nothing changes. If anything, the standards might be a little looser now.
For AcquiaPHP projects, see that the standard is slightly more strict and incorporates PSR-12 elements.
danepowell
commented
3 months ago
This is a ground-up rewrite of the Acquia PHP standard to be based on PSR-12 and compatible with Drupal standards. In other words, any code adhering to Acquia PHP will also adhere to Drupal standards, but not necessarily vice-versa.
This means that Acquia PHP is a stricter subset of PSR-12 and the Drupal standards, which is a paradigm shift from its original implementation as a looser standard (and hence, base of) the Drupal standards. This warrants a new major release.
PER isn't available in PHPCS yet, but the good news is it's mostly backwards-compatible (i.e., only contains additions for new PHP features) and can we can basically swap it in for PSR-12 when it lands: https://github.com/PHPCSStandards/PHP_CodeSniffer/issues/29
The best way to test this is against projects already on the latest version of the AcquiaPHP or AcquiaDrupal* standards.
Dependency changes