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
I've investigated this and the issue with the upstream sniff referred to is caused by all errors thrown by the sniff being reported on line 1.
This is not the case for the WordPress.WhiteSpace.PrecisionAlignment sniff which reports each issue on the line where it is found.
This means that no extra provisions need to be made for the new annotations in the WordPress.WhiteSpace.PrecisionAlignmentsniff.
However, they should possibly be made in the Files.FileName sniff, though it would be more customary for files to be excluded from that sniff from the ruleset.
All the same, I believe the sniff should respect the PHPCS annotations when found, so I'll look into fixing this.
PHPCS 3.2.0 will bring a new inline ignore annotations.
WPCS contains two sniffs which examine a complete file based on a
T_OPEN_TAG
.For the
Files.FileName
sniff, the changes are irrelevant in my opinion.However, the
WhiteSpace.PrecisionAlignment
sniff, should start to allow for the new annotations.The following two commits show how this is handled/fixed in one of the upstream sniffs:
The text was updated successfully, but these errors were encountered: