-
Normally, composer packages follow one of the standards: PEAR, Zend, PSR2, Squiz, PSR1, PSR12, Symfony etc.
Can we please pick one of the standards and follow them. Once decided on the standard, I …
-
In a large existing codebase, it usually not possible to fix all violations at once. Or when new violations appear when new rules are added. Think for example the Slevomat Coding Standard. This featur…
-
I'm using Intelephense with Symfony 7 and PHP 8.3.
As per PSR-12 documentation (4.4)
> The opening brace MUST go on its own line, and the closing brace MUST go on the next line following the bod…
-
Assume you have the following:
```php
-
Running phpcbf for PSR12 I get:
```
-
```php
class Foo
{
use Bar;
}
```
-
Good day!
Thank you for great extension!
The problem:
I get different results for formatting. Maybe extension does not pay attention to rulesets in the provided config file ?
For example,…
-
Lets assume we have the following folder structure:
- src
- plugins
- tests
- vendor
is there a way to provide multiple directories with the dir option like that?
name: PHP Code Style (phpcs…
-
Filipus Klutiero:
> Although PDT comes with a formatter profile implementing the deprecated PSR-2, it does not come with one implementing the newer PSR-12 "Extended Coding Style", also recommended …
zulus updated
2 years ago
-
[PSR-12](https://www.php-fig.org/psr/psr-12/) just got approved. [PER-CS v1](https://groups.google.com/g/php-fig/c/bBh4Y-R5gxE) is the same in terms of rules, so all the changes must be included in bo…