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: CHANGELOG.md
+11-1
Original file line number
Diff line number
Diff line change
@@ -10,12 +10,22 @@ This projects adheres to [Keep a CHANGELOG](http://keepachangelog.com/) and uses
10
10
_Nothing yet._
11
11
12
12
13
+
## [1.0.1] - 2020-06-28
14
+
15
+
### Changed
16
+
* The `master` branch has been renamed to `stable`.
17
+
* The version requirements for the [Dealerdirect Composer PHPCS plugin] have been widened to allow installation of releases from the `0.7.x` range, which brings compatibility with Composer 2.0.
18
+
* Miscellaneous updates to the development environment and CI scripts.
19
+
20
+
13
21
## 1.0.0 - 2020-02-12
14
22
15
23
Initial release containing:
16
24
* Feature completeness checking tool for PHPCS sniffs.
17
25
* A `PHPCSDebug` standard to help debugging sniffs.
[](https://github.com/PHPCSStandards/PHPCSDevTools/releases)
[](https://travis-ci.com/PHPCSStandards/PHPCSDevTools)
If you work on several different sniff repos, you may want to install this toolset globally:
45
45
```bash
46
-
composer global require phpcsstandards/phpcsdevtools:^1.0
46
+
composer global require --dev phpcsstandards/phpcsdevtools:^1.0
47
47
```
48
48
49
49
Composer will automatically install dependencies and register the PHPCSDebug standard with PHP_CodeSniffer using the [DealerDirect Composer PHPCS plugin](https://github.com/Dealerdirect/phpcodesniffer-composer-installer/).
@@ -59,7 +59,7 @@ Composer will automatically install dependencies and register the PHPCSDebug sta
**Warning**: :warning: The `installed_paths` command overwrites any previously set `installed_paths`. If you have previously set `installed_paths` for other external standards, run `phpcs --config-show` first and then run the `installed_paths` command with all the paths you need separated by comma's, i.e.:
62
+
:warning:**Warning**: The `installed_paths` command overwrites any previously set `installed_paths`. If you have previously set `installed_paths` for other external standards, run `phpcs --config-show` first and then run the `installed_paths` command with all the paths you need separated by comma's, i.e.:
### Checking whether all sniffs in a PHPCS standard are feature complete
72
72
73
-
You can now easily check whether each and every sniff in your standard is accompanied by a documentation XML file (warning) as well as unit test files (error).
73
+
You can now check whether each and every sniff in your standard is accompanied by a documentation XML file (warning) as well as unit test files (error).
74
74
75
-
To use the tool, run it from the root of the your standards repo like so:
75
+
To use the tool, run it from the root of your standards repo like so:
76
76
```bash
77
77
# When installed as a project dependency:
78
78
vendor/bin/phpcs-check-feature-completeness
@@ -122,7 +122,7 @@ Once this project is installed, you will see a new `PHPCSDebug` ruleset in the l
122
122
For now, this standard only contains one sniff: `PHPCSDebug.Debug.TokenList`.
123
123
This sniff will display compact, but detailed information about the tokens found in a (test case) file.
124
124
125
-
This sniff is compatible with PHPCS 3.0+.
125
+
This sniff is compatible with PHPCS 3.0.2+.
126
126
127
127
Typical usage:
128
128
* Set up a test case file for a new sniff you intend to write.
@@ -172,7 +172,7 @@ PHPCS itself can also display similar information using the `-vv` or `-vvv` verb
172
172
173
173
Contributing
174
174
-------
175
-
Contributions to this project are welcome. Just clone the repo, branch off from `develop`, make your changes, commit them and send in a pull request.
175
+
Contributions to this project are welcome. Clone this repository, branch off from `develop`, make your changes, commit them and send in a pull request.
176
176
177
177
If unsure whether the changes you are proposing would be welcome, open an issue first to discuss your proposal.
0 commit comments