You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: wiki/Version-1.3.0-Upgrade-Guide.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ The contents of this file will be minimal if you are not including any sniffs fr
30
30
</ruleset>
31
31
```
32
32
33
-
A simple `ruleset.xml` file like this tells PHP_CodeSniffer that this directory contains a coding standard, the name of the standard is *My Standard* and the sniffs in the standard are sourced directly from the default `Sniffs` directory.
33
+
A simple `ruleset.xml` file like this tells PHP_CodeSniffer that this directory contains a coding standard, the name of the standard is _My Standard_ and the sniffs in the standard are sourced directly from the default `Sniffs` directory.
34
34
35
35
Once you've created your `ruleset.xml` file, you can go ahead and delete the `CodingStandard.php` class file as it is no longer required. However, you can keep both files in the coding standard if you want to use your standard in both old and new versions of PHP_CodeSniffer. But be aware that you will need to make changes to both files and any advanced ruleset features you add to your `ruleset.xml` file can not be replicated in your `CodingStandard.php` class file.
0 commit comments