Expand Section 2.7 entry in the PER-CS 2.0 to 3.0 migration guide#146
Open
rodrigoprimo wants to merge 1 commit into
Open
Expand Section 2.7 entry in the PER-CS 2.0 to 3.0 migration guide#146rodrigoprimo wants to merge 1 commit into
rodrigoprimo wants to merge 1 commit into
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PER-CS 3.0 introduced a new Section 2.7. It adopts the php-src naming conventions for abbreviations and acronyms, quoting them directly:
In the spec, the SHOULD-avoid recommendation is the lead rule and the capitalization rule (
XmlFormatternotXMLFormatter) is the dependent follow-on. The migration guide's existing Section 2.7 entry covered only the capitalization rule and omitted the SHOULD-avoid recommendation entirely.This section was introduced by #102. This PR rewrites the entry so it leads with the SHOULD-avoid recommendation and keeps the capitalization rule as the follow-on.