wp-register-setting-fields/phpcs-format.xml.dist at main · arraypress/wp-register-setting-fields · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
<?xml version="1.0"?>
<ruleset name="Wp Register Setting Fields (formatting)">
    <description>Formatting and style. Separate from the lint: a clean lint does not mean a clean format check.</description>

    <file>src</file>

    <arg name="extensions" value="php"/>
    <arg name="colors"/>
    <arg value="sp"/>

    <config name="installed_paths" value="vendor/wp-coding-standards/wpcs,vendor/phpcompatibility/php-compatibility,vendor/phpcompatibility/phpcompatibility-paragonie,vendor/phpcompatibility/phpcompatibility-wp,vendor/phpcsstandards/phpcsutils,vendor/phpcsstandards/phpcsextra"/>

    <rule ref="WordPress-Core">
        <exclude name="Universal.Arrays.DisallowShortArraySyntax"/>
        <exclude name="WordPress.PHP.YodaConditions"/>
        <exclude name="Generic.WhiteSpace.DisallowSpaceIndent"/>
        <exclude name="Generic.WhiteSpace.ScopeIndent"/>
        <exclude name="PEAR.Functions.FunctionCallSignature"/>
        <exclude name="Squiz.Commenting.FileComment"/>
        <exclude name="Universal.Operators.DisallowShortTernary"/>
        <exclude name="Generic.Formatting.MultipleStatementAlignment"/>
        <exclude name="WordPress.Arrays.MultipleStatementAlignment"/>
    </rule>

    <rule ref="WordPress.Security.EscapeOutput">
        <!--
            Every one of these echoes the return value of an EDD markup helper:
            EDD()->html->select(), ->product_dropdown(), ->date_field() and the
            rest. They return escaped HTML by design, and escaping the result
            again would print the tags instead of rendering the controls.
            Rendering EDD's own fields is what this library is for, so the
            exclusion is the whole file rather than a line list.
        -->
    </rule>


    <rule ref="WordPress.Files.FileName">
        <!--
            Off, not waived. This is a Composer library autoloaded by PSR-4,
            which requires the file to be named for the class it declares:
            Exporters.php. WordPress wants class-exporters.php. The two rules
            are mutually exclusive, and renaming the files to satisfy this one
            would stop the autoloader finding them at all.
        -->
        <exclude-pattern>*</exclude-pattern>
    </rule>


    <rule ref="Universal.Operators.StrictComparisons">
        <!--
            Conditional-field logic compares a value that came off an HTML form
            — always a string — against a value declared in PHP config, which
            is commonly an int or a bool. `'1' == 1` has to hold, or a field
            declared with `'value' => 1` would never match the posted `'1'` and
            conditional visibility would never fire. Several call sites already
            pass `false` explicitly as in_array()'s $strict argument, which is
            the same decision written down. Making these strict is a
            regression, not a fix.
        -->
        <exclude-pattern>src/Traits/ConditionalLogic.php</exclude-pattern>
    </rule>

    <rule ref="WordPress.PHP.StrictInArray">
        <!-- Same reason as Universal.Operators.StrictComparisons above. -->
        <exclude-pattern>src/Traits/ConditionalLogic.php</exclude-pattern>
        <exclude-pattern>src/Traits/Rendering/ChoiceFields.php</exclude-pattern>
        <exclude-pattern>src/Traits/Rendering/NestedFields.php</exclude-pattern>
    </rule>

</ruleset>