From 0aa4c04a067f356be715c728fa5f3b73cce7fada Mon Sep 17 00:00:00 2001 From: Rodrigo Primo Date: Wed, 27 May 2026 14:48:51 +0000 Subject: [PATCH] Expand Section 6.4 entry in the PER-CS 2.0 to 3.0 migration guide Section 6.4 is new in 3.0. Among its rules, ternaries MUST occupy 3 lines, never 2. The migration guide already has a Section 6.4 entry covering the general operator-at-start rule, but it omits the ternary-specific constraint. This commit appends the missing sentence to that entry. --- 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..86ec3b0 100644 --- a/migration-3.0.md +++ b/migration-3.0.md @@ -137,7 +137,7 @@ When breaking a series of boolean operators across multiple lines, the operator ## [Section 6.4 - Operator placement](https://www.php-fig.org/per/coding-style/#64-operator-placement) -When breaking a series of chained operations across multiple lines, the operator MUST be at the beginning of each line, not the end of each line, and all lines but the first MUST be indented. Examples include `??` and ternary conditionals. +When breaking a series of chained operations across multiple lines, the operator MUST be at the beginning of each line, not the end of each line, and all lines but the first MUST be indented. Examples include `??` and ternary conditionals. Ternaries MUST occupy 3 lines, never 2. ```php