-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathruleset.xml
More file actions
executable file
·97 lines (76 loc) · 3.07 KB
/
ruleset.xml
File metadata and controls
executable file
·97 lines (76 loc) · 3.07 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
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
<?xml version="1.0"?>
<ruleset name="ZendNew">
<description>The new Zend framework coding standard
(according to http://framework.zend.com/manual/en/coding-standard.html).</description>
<!-- This is basically the PEAR standard with customizations... -->
<rule ref="PEAR">
<exclude name="PEAR.Commenting.FileComment" />
<exclude name="PEAR.Commenting.ClassComment" />
<exclude name="PEAR.Commenting.FunctionComment" />
<exclude name="PEAR.NamingConventions.ValidVariableName" />
<exclude name="PEAR.NamingConventions.ValidFunctionName" />
<exclude name="PEAR.WhiteSpace.ScopeIndent" />
<exclude name="PEAR.Files.IncludingFile" />
</rule>
<!-- ZF coding standard doesn't say anything
about version tags other than that they have to exist. -->
<rule ref="PEAR.Commenting.FileComment.InvalidVersion">
<severity>0</severity>
</rule>
<!-- ZF coding standard doesn't care where the equal-sign is on
multiple assignments -->
<rule ref="PEAR.Formatting.MultiLineAssignment.EqualSignLine">
<severity>0</severity>
</rule>
<!-- ZF coding standard doesn't say, that the closing bracket has to
be on a new line -->
<rule ref="PEAR.ControlStructures.MultiLineCondition.CloseBracketNewLine">
<severity>0</severity>
</rule>
<!-- ZF coding standard doesn't care about the php-version -->
<rule ref="ZendNew.Commenting.FileComment.MissingVersion">
<severity>0</severity>
</rule>
<!-- Include some additional sniffs from the Generic standard -->
<rule ref="Generic.Functions.FunctionCallArgumentSpacing"/>
<rule ref="Generic.NamingConventions.UpperCaseConstantName"/>
<rule ref="Generic.PHP.LowerCaseConstant"/>
<rule ref="Generic.PHP.DisallowShortOpenTag"/>
<rule ref="Generic.WhiteSpace.DisallowTabIndent"/>
<rule ref="Generic.WhiteSpace.ScopeIndent"/>
<!-- Include some additional sniffs from the Squiz standard -->
<rule ref="Squiz.WhiteSpace.OperatorSpacing"/>
<!-- TEMPORARILY DISABLE CAMELCAPS SNIFF! -->
<rule ref="ZendNew.NamingConventions.ValidVariableName.NotCamelCaps">
<severity>0</severity>
</rule>
<rule ref="ZendNew.NamingConventions.ValidVariableName.StringNotCamelCaps">
<severity>0</severity>
</rule>
<rule ref="ZendNew.NamingConventions.ValidVariableName.MemberNotCamelCaps">
<severity>0</severity>
</rule>
<!-- Lines can be 85 chars long, but never show errors -->
<rule ref="Generic.Files.LineLength">
<properties>
<property name="lineLimit" value="120"/>
<property name="absoluteLineLimit" value="120"/>
</properties>
</rule>
<!-- Use Unix newlines -->
<rule ref="Generic.Files.LineEndings">
<properties>
<property name="eolChar" value="\n"/>
</properties>
</rule>
<!-- This messgae is not required as spaces are allowed for alignment -->
<rule ref="Generic.Functions.FunctionCallArgumentSpacing.TooMuchSpaceAfterComma">
<severity>0</severity>
</rule>
<!-- Use warnings for inline control structures -->
<rule ref="Generic.ControlStructures.InlineControlStructure">
<properties>
<property name="error" value="false"/>
</properties>
</rule>
</ruleset>