|
| 1 | +<?xml version="1.0"?> |
| 2 | +<ruleset name="AvoRed Coding Standards"> |
| 3 | + |
| 4 | + <!-- |
| 5 | + The name attribute of the ruleset tag is displayed |
| 6 | + when running PHP_CodeSniffer with the -v command line |
| 7 | + argument. The description tag below is not displayed anywhere |
| 8 | + except in this file, so it can contain information for |
| 9 | + developers who may change this file in the future. |
| 10 | + --> |
| 11 | + <description>The AvoRed Coding Standards</description> |
| 12 | + |
| 13 | + <!-- |
| 14 | + If no files or directories are specified on the command line |
| 15 | + your custom standard can specify what files should be checked |
| 16 | + instead. |
| 17 | + Note that specifying any file or directory path |
| 18 | + on the command line will ignore all file tags. |
| 19 | + --> |
| 20 | + <file>src/Permission</file> |
| 21 | + |
| 22 | + <!-- |
| 23 | + You can hard-code ignore patterns directly into your |
| 24 | + custom standard so you don't have to specify the |
| 25 | + patterns on the command line. |
| 26 | + --> |
| 27 | + <exclude-pattern>*/config/*</exclude-pattern> |
| 28 | + <exclude-pattern>*/database/*</exclude-pattern> |
| 29 | + <exclude-pattern>*/resources/*</exclude-pattern> |
| 30 | + <exclude-pattern>*/routes/*</exclude-pattern> |
| 31 | + <exclude-pattern>*/tests/*</exclude-pattern> |
| 32 | + |
| 33 | + <!-- |
| 34 | + You can hard-code command line values into your custom standard. |
| 35 | + Note that this does not work for the command line values: |
| 36 | + -v[v][v], -l, -d, -sniffs and -standard |
| 37 | + The following tags are equivalent to the command line arguments: |
| 38 | + -p |
| 39 | + --> |
| 40 | + <arg name="colors"/> |
| 41 | + |
| 42 | + <!-- |
| 43 | + You can hard-code custom php.ini settings into your custom standard. |
| 44 | + The following tag sets the memory limit to 64M. |
| 45 | + --> |
| 46 | + <ini name="memory_limit" value="128M"/> |
| 47 | + |
| 48 | + <!-- |
| 49 | + Include all sniffs in the PEAR standard. Note that the |
| 50 | + path to the standard does not have to be specified as the |
| 51 | + PEAR standard exists inside the PHP_CodeSniffer install |
| 52 | + directory. |
| 53 | + --> |
| 54 | + <rule ref="PEAR"> |
| 55 | + <exclude name="PEAR.Commenting.FileComment" /> |
| 56 | + <exclude name="PEAR.Commenting.ClassComment" /> |
| 57 | + <exclude name="PEAR.Commenting.FunctionComment" /> |
| 58 | + </rule> |
| 59 | + |
| 60 | + <rule ref="PEAR"> |
| 61 | + <exclude name="Generic.Commenting.DocComment" /> |
| 62 | + </rule> |
| 63 | + |
| 64 | +</ruleset> |
0 commit comments