phpmd.xml

<?xml version="1.0"?>
<ruleset name="pipelinq"
    xmlns="http://pmd.sourceforge.net/ruleset/2.0.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://pmd.sourceforge.net/ruleset/2.0.0 http://pmd.sourceforge.net/ruleset_xml_schema.xsd">
    <description>pipelinq — Conduction PHPMD ruleset (single source: conduction/hydra-gates).</description>

    <rule ref="vendor/conduction/hydra-gates/quality-config/phpmd.xml">
        <exclude name="StaticAccess"/>
    </rule>

    <!-- StaticAccess: one exception, and only one.

         `\OCA\Pipelinq\Support\FleetAppId` is a pure resolver over a constant
         map: given an IAppManager and a canonical app name, it returns whichever
         id the instance actually registered. It holds no state and no
         collaborators — it takes the only thing it needs as an argument — so
         there is nothing here that could be injected. Making it a service would
         add DI wiring around a lookup table.

         It also exists to be DELETED. It bridges the window where `development`
         carries the new fleet app ids and `beta`/`main` still carry the old
         ones; once those agree, every call site becomes a plain string again and
         the class goes away.

         This uses the rule's OWN `exceptions` property — its designed
         configuration surface — rather than an @SuppressWarnings annotation or a
         baseline entry. The rule stays fully active for every other class, and
         the exception is one named class, visible in config, with the reason
         attached. -->
    <rule ref="rulesets/cleancode.xml/StaticAccess">
        <properties>
            <property name="exceptions" value="\OCA\Pipelinq\Support\FleetAppId"/>
        </properties>
    </rule>
</ruleset>