[JanTvrdik]

A suppression comment that names a message code of a sniff, and not the sniff itself, was neither honored nor migrated:

public $First_Name; // phpcs:ignore Squiz.NamingConventions.ValidVariableName.MemberNotCamelCaps

Translator::findPaths() knew Squiz.NamingConventions.ValidVariableName, but not its message codes, so PluginRegistry::expandSuppressedName() returned nothing and the report stayed. phpcs prints these codes with -s, so projects write them often (the code base we are moving to DressCode has 33 of this one).

The table already has rows for single messages (Squiz.WhiteSpace.OperatorSpacing.Unary, Squiz.Commenting.FunctionComment.DuplicateReturn). This PR adds rows for the naming messages whose check DressCode has:

message	decision
Squiz.NamingConventions.ValidVariableName.MemberNotCamelCaps	naming.property
Squiz.NamingConventions.ValidVariableName.NotCamelCaps, .StringNotCamelCaps	naming.variable
PSR1.Methods.CamelCapsMethodName.NotCamelCaps	naming.method
Generic.NamingConventions.UpperCaseConstantName.ClassConstantNotUpperCase	naming.constant (phpcs reports every const with it)

A suppression now silences what its message was about and nothing more: MemberNotCamelCaps silences naming.property, not naming.variable. A message without a row still silences nothing, as before. migrate-suppressions and suppressionComments read the same method, so they follow.

What the rows leave out:

• UpperCaseConstantName.ConstantNotUpperCase gets no row: phpcs reports it only for define(), which DressCode does not check.
• ValidVariableName.NotCamelCaps is also what phpcs reports for a promoted constructor parameter, which DressCode checks under naming.property, so such a suppression does not silence it. The row does not add naming.property, because a ruleset enabling NotCamelCaps alone would then check every property.

The rows also reach dresscode import:

• A ruleset that enables a message alone (<rule ref="PSR1.Methods.CamelCapsMethodName.NotCamelCaps"> with an exclude pattern) now translates to its decision instead of "cannot enable alone".
• A message excluded while the ruleset turns its sniff on by name (ValidVariableName on, .MemberNotCamelCaps excluded) would give a keep that the sniff's own set overrides, so naming.property would silently stay camelCase. translateDisabled() now says instead that the excluded message cannot leave out what its sniff sets, the warning it gives for a message without a row. This also adds the warning to a row that existed: SwitchDeclaration on by name with .SpaceBeforeColonCASE excluded, which kept spacing.switchCase without a word. Where the sniff comes in through a standard (PSR12 with .SpaceBeforeColonCASE excluded), the keep still wins, as before.
• PSR12 with PSR1.Methods.CamelCapsMethodName.NotCamelCaps excluded keeps naming.method as before, but the warning is now the one of a sniff turned off ("naming.method also stands for …").

Tests: tests/DressCode/Config/PluginRegistry.phpt (the new rows, a row that existed, a message without a row), tests/DressCode/Interop/Translator.phpt (a message enabled alone, a message excluded while its sniff is on by name).

Locally, all checks give the same results as on master: the forbiddenPhpdocLines fixture fails, and PHPStan reports the error in tests/bootstrap.php, plus three errors in NativeType.php and PhpdocTypeNotationVisitor.php with a fresh composer install (phpstan/phpdoc-parser 2.4.0). Upstream CI has not run on this PR yet.

Co-Authored-By: Claude Code

https://claude.ai/code/session_01D1mfZTuCXTAaFC39NM1xdk

[Copilot]

🟢 Approval recommended

No active review issues were identified for the suppression-lookup changes.

No open issues 🎉

What changed in this PR

This PR makes DressCode honor PHP_CodeSniffer suppression comments that name a sniff’s message code, and enables migrate-suppressions to translate those comments through the same lookup.

Changes:

• Falls back from an untranslated four-part message code to its parent sniff’s decisions, while preserving explicit message-code translations.
• Adds regression coverage for a recognized sniff message and an unknown name.

File	Description
tests/​DressCode/​Config/​PluginRegistry.phpt	Tests message-code fallback and unknown-name handling.
src/​Config/​PluginRegistry.php	Implements and documents parent-sniff fallback for suppression lookup.

_{Review effort: Balanced}

[dg]

Thank you! Merged into master with one change: a message excluded while its sniff is turned on by name now makes what it stands for keep, the same as when the sniff comes from a standard, instead of keeping the sniff's value with a warning. A project with ValidVariableName on and MemberNotCamelCaps excluded keeps its snake_case properties, which is what it asked for.