PSR1/SideEffects: improve recognition of disable/enable annotations #3772
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.
As it was, the sniff would respect PHPCS disable annotations, but only when either unqualified or qualified up to a sniff name. It would not respect a disable annotation using a sniffname with errorcode, i.e.
PSR1.Files.SideEffects.FoundWithSymbols
.While the
FoundWithSymbols
errorcode is the only error code for this sniff and using// phpcs:disable PSR1.Files.SideEffects.FoundWithSymbols
is effectively the same as using// phpcs:disable PSR1.Files.SideEffects
, I do believe end-users should not need to be aware of whether or not a sniff has multiple error codes when using disable annotations.This updates the sniff to also respect disable annotations which include the error code.
Includes unit test.
Fixes #3386