You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I'm not mistaken, PEAR.Functions.FunctionCallSignature sniff should handle it, and we are including it in the WordPress-Core ruleset. Once we up the requirement of PHPCS to 3.7.0, we should just add extra test cases to see if it's handled correctly.
Since PHP 7.3, adding a trailing comma in function calls, like:
won't throw a parse error.
This has been motivated by the fact that you could have a trailing comma in an array declaration since always:
and in grouped namespace syntax since PHP 7.2:
There are examples of what's not allowed in the RFC.
If I'm not mistaken,
PEAR.Functions.FunctionCallSignature
sniff should handle it, and we are including it in the WordPress-Core ruleset. Once we up the requirement of PHPCS to 3.7.0, we should just add extra test cases to see if it's handled correctly.Refs:
Related to #764
The text was updated successfully, but these errors were encountered: