Skip to content

Rewrite Section 4.6 entry in the PER-CS 2.0 to 3.0 migration guide #145

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
rodrigoprimo wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Rewrite Section 4.6 entry in the PER-CS 2.0 to 3.0 migration guide #145

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions migration-3.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,17 +75,19 @@ class Foo

## [Section 4.6 - Modifier Keywords](https://www.php-fig.org/per/coding-style/#46-modifier-keywords)

At least one of `readonly`, `get`-visibility, and `set`-visibility must be specified. If at least one is specified, the others may be omitted.
The set-visibility modifier (`public(set)`, `protected(set)`, `private(set)`) was added to the modifier ordering, between the general visibility and the `static` modifier.

All modifier keywords MUST be all lower-case. The `public` keyword MAY be omitted when using a set-visibility on a public-read property.

```php
class Foo
{
// These are all acceptable.
public private(set) string $one;
private(set) string $two;
readonly string $three;

// These are not.
PUBLIC PROTECTED(set) string $three;
private(set) public string $four;
}
```
Expand Down