Skip to content

Expand Section 2.7 entry in the PER-CS 2.0 to 3.0 migration guide #146

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

Expand Section 2.7 entry in the PER-CS 2.0 to 3.0 migration guide #146

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
2 changes: 1 addition & 1 deletion migration-3.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@ function veryComplex(

## [Section 2.7 - Naming](https://www.php-fig.org/per/coding-style/#27-naming)

PER-CS now recommends following the same naming conventions as PHP Internals for abbreviations and acronyms. Specifically, only uppercase the first character of the acronym: `XmlFormatter`, not `XMLFormatter`.
PER-CS now recommends following the same naming conventions as PHP Internals for abbreviations and acronyms. Abbreviations, acronyms, and initialisms SHOULD be avoided wherever possible, unless they are much more widely used than the long form (e.g. `HTTP` or `URL`). When they are used, only the first character should be uppercased: `XmlFormatter`, not `XMLFormatter`.

## [Section 3 - Declare Statements, Namespace, and Import Statements](https://www.php-fig.org/per/coding-style/#3-declare-statements-namespace-and-import-statements)

Expand Down