Upstream (Squiz) updates#4
Merged
Merged
Conversation
… for PSR2 code style
…t properly recognize last use
…ligned argument comments when they are blank
…defect a PEAR install and only use the data dir in that case. This allows composer installs to write a new CodeSniffer.conf file that is not tracked in git and so is not overwritten with each update.
… using curly braces
Conflicts: CodeSniffer.conf We have the .conf set to use our standard but the file was removed upstream; we're going to continue to use the existing .conf file.
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
3 participants
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.
No description provided.