This repository was archived by the owner on Mar 13, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathphpcs.xml
More file actions
80 lines (66 loc) · 3.53 KB
/
Copy pathphpcs.xml
File metadata and controls
80 lines (66 loc) · 3.53 KB
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
72
73
74
75
76
77
78
79
80
<?xml version="1.0"?>
<ruleset xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="BCGov Coding Standards" xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/squizlabs/PHP_CodeSniffer/master/phpcs.xsd">
<description>BCGov Coding Standards overrides</description>
<!-- Exclude the Composer Vendor directory. -->
<exclude-pattern>/vendor/*</exclude-pattern>
<!-- Exclude the Node Modules directory. -->
<exclude-pattern>/node_modules/*</exclude-pattern>
<!-- Exclude minified Javascript files. -->
<exclude-pattern>*.min.js</exclude-pattern>
<exclude-pattern>*.js</exclude-pattern>
<exclude-pattern>/tests/_*</exclude-pattern>
<!-- Include the WordPress-Extra standard. -->
<rule ref="WordPress-Extra">
<!--
We may want a middle ground though. The best way to do this is add the
entire ruleset, then rule by rule, remove ones that don't suit a project.
We can do this by running `phpcs` with the '-s' flag, which allows us to
see the names of the sniffs reporting errors.
Once we know the sniff names, we can opt to exclude sniffs which don't
suit our project like so.
The below two examples just show how you can exclude rules.
They are not intended as advice about which sniffs to exclude.
-->
<!--
<exclude name="WordPress.WhiteSpace.ControlStructureSpacing"/>
<exclude name="WordPress.Security.EscapeOutput"/>
-->
</rule>
<!-- Let's also check that everything is properly documented. -->
<rule ref="WordPress-Docs"/>
<!-- Add in some extra rules from other standards. -->
<rule ref="Generic.CodeAnalysis.UnusedFunctionParameter"/>
<rule ref="Generic.Commenting.Todo"/>
<rule ref="Generic.WhiteSpace.DisallowSpaceIndent.SpacesUsed" ><severity>0</severity></rule>
<rule ref="Generic.Arrays.DisallowShortArraySyntax.Found" ><severity>0</severity></rule>
<rule ref="Squiz.Commenting.FileComment.Missing"><severity>0</severity></rule>
<rule ref="Squiz.Commenting.FileComment.SpacingAfterComment"><severity>0</severity></rule>
<rule ref="WordPress.WP.I18n.TextDomainMismatch"><severity>0</severity></rule>
<rule ref="WordPress.WhiteSpace.PrecisionAlignment.Found"><severity>0</severity></rule>
<rule ref="WordPress.NamingConventions.PrefixAllGlobals.NonPrefixedFunctionFound"><severity>0</severity></rule>
<rule ref="WordPress.NamingConventions.PrefixAllGlobals.NonPrefixedVariableFound"><severity>0</severity></rule>
<rule ref="WordPress.NamingConventions.PrefixAllGlobals.NonPrefixedNamespaceFound"><severity>0</severity></rule>
<!--<rule ref="WordPress.NamingConventions.PrefixAllGlobals.NonPrefixedNamespaceFound"><type>warning</type></rule>-->
<rule ref="WordPress.Files.FileName.InvalidClassFileName"><severity>0</severity></rule>
<rule ref="Squiz.Commenting.FunctionComment.SpacingAfterParamType"><severity>0</severity></rule>
<!-- gives warning if there is no domain after __('string', domain) -->
<rule ref="WordPress.WP.I18n.MissingArgDomain"><severity>0</severity></rule>
<!-- gives warning if there isn't a comment after parameter -->
<rule ref="Squiz.Commenting.FunctionComment.MissingParamComment"><severity>0</severity></rule>
<config name="minimum_supported_wp_version" value="4.7"/>
<rule ref="WordPress.WP.I18n">
<properties>
<property name="text_domain" type="array">
<element value="my-textdomain"/>
<element value="library-textdomain"/>
</property>
</properties>
</rule>
<rule ref="WordPress.NamingConventions.PrefixAllGlobals">
<properties>
<property name="prefixes" type="array">
<element value="my_prefix"/>
</property>
</properties>
</rule>
</ruleset>