-
[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…
-
## Affected Version
5.x-dev
## Description
A set of PSR-2 rules are ignored for framework, specifically because fixing them would require breaking changes to code. These exclusions are necess…
-
In order to avoid any potential conflicts with other plugins, it's better to use namespaced classes. An added perk is using PSR-12 autoloading. Even if WordPress is not implementing PSR-12 autoloading…
-
We now have these guidelines: https://github.com/cypht-org/cypht/wiki/Contributing
"closer adherence to PSR-12 syntax guidelines" was done here: https://github.com/cypht-org/cypht/pull/948
Tiki.…
-
Just a hint: https://www.php-fig.org/psr/psr-12/ 🙂
Hope netbeans will be able to support it
-
Now that PSR12 has been ~~released~~ accepted, when will we see an update to include it as part of the ruleset?
https://github.com/squizlabs/PHP_CodeSniffer/blob/master/src/Standards/PSR12/ruleset.…
-
It is our intention to follow psr-12 `Extended Coding Style Guide` (https://github.com/php-fig/fig-standards/blob/master/proposed/extended-coding-style-guide.md) if/when it passes. Even if it contradi…
-
The shot_record.php file contains inconsistencies in naming conventions. According to PSR-12 guidelines, variable and function names should follow camelCase for PHP code. However, the file in question…
-
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
-
> **Disclaimer:** I am aware that it's not make-or-break for Prettier to adhere to PSR-12.
>
> However, now that it is officially accepted as a standard, we should discuss (and, if necessary, reject…
loilo updated
4 years ago