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: .github/CONTRIBUTING.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,17 +31,17 @@ Alternatively, if you have push access to this repo, create a feature branch pre
31
31
## Public properties
32
32
33
33
When writing sniffs, always remember that any `public` sniff property can be overruled via a custom ruleset by the end-user.
34
-
Only make a property `public` if that is the intended behaviour.
34
+
Only make a property `public` if that is the intended behavior.
35
35
36
36
When you introduce new `public` sniff properties, or your sniff extends a class from which you inherit a `public` property, please don't forget to update the [public properties wiki page](https://github.com/WordPress/WordPress-Coding-Standards/wiki/Customizable-sniff-properties) with the relevant details once your PR has been merged into the `develop` branch.
37
37
38
38
# Unit Testing
39
39
40
40
## Pre-requisites
41
41
* WordPress-Coding-Standards
42
-
* PHP_CodeSniffer 3.9.0 or higher
43
-
* PHPCSUtils 1.0.10 or higher
44
-
* PHPCSExtra 1.2.1 or higher
42
+
* PHP_CodeSniffer 3.13.0 or higher
43
+
* PHPCSUtils 1.1.0 or higher
44
+
* PHPCSExtra 1.4.0 or higher
45
45
* PHPUnit 4.x - 9.x
46
46
47
47
The WordPress Coding Standards use the `PHP_CodeSniffer` native unit test framework for unit testing the sniffs.
0 commit comments