Description: ------------ 1) Opening parenthesis of a multi-line function call must be the last content on the line. 2) Closing parenthesis of a multi-line function call must be on a line by itself These 2 sniffs are not in the PSR2 standard and were inherited from PEAR

The sniff was not inherited from the PEAR standard; it was specifically selected so that it could implement part of the PSR2 standard. See the ruleset here: https://github.com/squizlabs/PHP_CodeSniffer/blob/master/CodeSniffer/Standards/ PSR2/ruleset.xml#L133 Standards grab sniffs from other standards so they don't duplicate code. It's a core feature of PHP_CodeSniffer's standard implementation. The code may refer to PEAR, but that is only to allow you to see where the sniff exists and to let you override the error messages globally. If you want to see where all the sniffs are coming from to generate the PSR2 standard, run: phpcs -e --standard=PSR2 Only 9 of the 40 sniffs are actually PSR2-specific.

I got it, but this rule is not part of PSR-2 Standard. So this sniff need to be removed.

Yes, it is part of the PSR-2 standard. https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style- guide.md#46-method-and-function-calls "Argument lists MAY be split across multiple lines, where each subsequent line is indented once. When doing so, the first item in the list MUST be on the next line, and there MUST be only one argument per line." Also look at the example code under that text.

I'm not talking about method declaration, but function call. See: $this->myFunction(array( 'test1', 'test2', )); OR throw new InvalidArgumentException(sprintf( '%s is invalid', $param )); This is valid in PSR-2

If you visited the link I provided, you'll see that it points to section 4.6. Method and Function Calls of the PSR-2 standard. We're talking about the same thing. What you have is not valid as per that part of the standard. It clearly states that you MAY split your call over multiple lines (obviously when you arg list makes it necessary) and that if you do, you MUST start the first item on the next line. Please note that there is a section in the standard about method declarations which defines the exact same rule. These are different rules, but use almost the same text.

Oh! Now I got it, thanks!

See https://github.com/zendframework/zf2/issues/4390

I've commented on the issue you submitted. There is no need to reopen this report. If the standard is clarified, I will make the changes to PHP_CodeSniffer without prompting. Thanks for linking the issue. It gave me a chance to comment somewhere it might be discussed more widely.