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
Also you can run `phpcbf` from the command-line to fix your code `MyAwesomeExtension` for warnings like
48
-
"PHPCBF CAN FIX THE [0-9]+ MARKED SNIFF VIOLATIONS AUTOMATICALLY"
60
+
61
+
Also, you can run `phpcbf` from the command-line to fix your code `MyAwesomeExtension` for warnings like "PHPCBF CAN FIX THE [0-9]+ MARKED SNIFF VIOLATIONS AUTOMATICALLY"
See the community [contribution model](https://github.com/magento/magento-coding-standard/blob/develop/.github/CONTRIBUTING.md).
70
+
71
+
### Where to contribute
72
+
54
73
- Documentation of existing rules. See [ExtDN PHP CodeSniffer rules for Magento 2](https://github.com/extdn/extdn-phpcs) as a good example.
55
74
- Bug fixes and improvements of existing rules.
56
75
- Creation of new PHP CodeSniffer rules.
57
76
- Discussions on new rules (through periodic hangouts or discussions per GitHub issue).
58
77
59
-
## How to contribute
78
+
### How to contribute
79
+
60
80
1) Start with looking into [Community Dashboard](https://github.com/magento/magento-coding-standard/projects/1). Any ticket in `Up for grabs` is a good candidate to start.
61
81
2) Didn't satisfy your requirements? [Create one of three types of issues](https://github.com/magento/magento-coding-standard/issues/new/choose):
62
82
-**Bug report** - Found a bug in the code? Let us know!
63
83
-**Existing rule enhancement** - Know how to improve existing rules? Open an issue describe how to enhance Magento Coding Standard.
64
84
-**New rule proposal** - Know how to improve Magento ecosystem code quality? Do not hesitate to open a proposal.
65
-
3) The issue will appear in the `Backlog` column of the [Community Dashboard](https://github.com/magento/magento-coding-standard/projects/1). Once it will be discussed and get `Accepted` label the issue will appear in the `Up for grabs` column.
85
+
3) The issue will appear in the `Backlog` column of the [Community Dashboard](https://github.com/magento/magento-coding-standard/projects/1). Once it will be discussed and get `accepted` label the issue will appear in the `Up for grabs` column.
66
86
67
87
## Testing
68
-
All rules should be covered by unit tests. Each `Test.php` class should be accompanied by a `Test.inc` file to allow for unit testing based upon the PHP CodeSniffer parent class `AbstractSniffUnitTest`.
88
+
89
+
All rules should be covered by unit tests. Each `Test.php` class should be accompanied by a `Test.inc` file to allow for unit testing based upon the PHP_CodeSniffer parent class `AbstractSniffUnitTest`.
69
90
You can verify your code by running
70
-
```
71
-
$ vendor/bin/phpunit
91
+
92
+
```bash
93
+
vendor/bin/phpunit
72
94
```
73
95
74
96
Also, verify that the sniffer code itself is written according to the Magento Coding Standard:
Each Magento source file included in this distribution is licensed under OSL-3.0 license.
81
103
82
-
Please see [LICENSE.txt](https://github.com/magento/magento-coding-standard/blob/master/LICENSE.txt) for the full text of the [Open Software License v. 3.0 (OSL-3.0)](http://opensource.org/licenses/osl-3.0.php).
104
+
Each Magento source file included in this distribution is licensed under the OSL-3.0 license.
105
+
106
+
Please see [LICENSE.txt](https://github.com/magento/magento-coding-standard/blob/master/LICENSE.txt) for the full text of the [Open Software License v. 3.0 (OSL-3.0)](https://opensource.org/licenses/osl-3.0.php).
0 commit comments