per-coding-style
per-coding-style copied to clipboard
php-fig
PER coding style
As per 4.3: > Visibility MUST be declared on all constants if your project > PHP minimum version supports constant visibilities > (PHP 7.1 or later).
Resolves #98. This seems the obvious way to do it. I debated the RECOMMENDED part. I'm open to changing that if other WG members feel strongly about it. WG members...
## 📚 Description Remove contradictory statements from some sections of the document. 👉🏼 https://github.com/php-fig/per-coding-style/pull/93#discussion_r1802870671 > Thanks @TimWolla for spotting the error :octocat:
[Property hooks](https://wiki.php.net/rfc/property-hooks) are landing in 8.4, the next version of PER-CS should cover them: ```php class Foo { public function __construct(private User $user) {} public string $userName { get {...
Resolves #91. WG members (only): Please 👍 this thread to indicate your approval, or comment to the contrary.
Resolves #95 This is largely just a direct copy from php-src, as planned. All I did was make the "shoulds" capitalized. WG members (only): Please 👍 this thread to indicate...
A new PHP release is coming soon, so it's time to get down and catch up on PER-CS! My expectation is that the next release will be 2.1, not 3.0...
[`new Foo()->baz()`](https://wiki.php.net/rfc/new_without_parentheses) will be allowed in PHP 8.4, we should cover it in the next version of PER-CS. To me this is similar to the question of `new Foo` vs...
https://wiki.php.net/rfc/asymmetric-visibility-v2 ```php class Foo { PRIVATE(set) string $bar1 = ''; public private(SET) string $bar2 = ''; private(set) public string $bar3 = ''; public function __construct( public protected(SET) string $bar4 =...
Replaces #83 PHP Internals has adopted guidelines for when and how to handle capitalization of abbreviations in class/method names. We should follow suit and just steal their language directly, and/or...