From 1ff46febc931a052443eb659dd25bf238d9edaed Mon Sep 17 00:00:00 2001 From: Rodrigo Primo Date: Wed, 27 May 2026 18:24:06 +0000 Subject: [PATCH] Expand Section 2.7 entry in the PER-CS 2.0 to 3.0 migration guide PER-CS 3.0 introduced a new 2.7 section. The migration guide's existing Section 2.7 entry covered the second part of the rule and omitted the SHOULD-avoid recommendation entirely. This commit rewrites the entry so it leads with the SHOULD-avoid rule and keeps the capitalization rule as the follow-on, matching the order in the spec. --- migration-3.0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/migration-3.0.md b/migration-3.0.md index 409a868..478a1cc 100644 --- a/migration-3.0.md +++ b/migration-3.0.md @@ -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)