Very very early draft for mail to funders about the 4.0 release #56
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
||
| ## Highlights of the 4.0 release | ||
|
|
||
| * Root rulesets can now overrule config and CLI settings set in child rulesets. |
There was a problem hiding this comment.
Suggested change
| * Root rulesets can now overrule config and CLI settings set in child rulesets. | |
| ### Root rulesets can now overrule config and CLI settings set in child rulesets. | |
| <config> directives set in the "root" ruleset are now prioritized over directives in included rulesets. Reminder: When two included rulesets at the same nesting level both set the same directive, the value from the last included ruleset gets prioritized. This has not changed. |
| ## Highlights of the 4.0 release | ||
|
|
||
| * Root rulesets can now overrule config and CLI settings set in child rulesets. | ||
| * Ability to scan files without extension. |
There was a problem hiding this comment.
Suggested change
| * Ability to scan files without extension. | |
| ### Scanning files without extension. | |
| Files without extensions are no longer ignored. That is, if users explicitly pass them on the command line or specify them in a ruleset. When users scan directories recursively, however, files without extensions will still be ignored. |
| @@ -0,0 +1,20 @@ | |||
| # PRESS RELEASE | |||
There was a problem hiding this comment.
Suggested change
| # PRESS RELEASE | |
| # PHPCS 4.0 is now available - Thanks to your support! |
| * Root rulesets can now overrule config and CLI settings set in child rulesets. | ||
| * Ability to scan files without extension. | ||
| * Less chance on scans failing on parse errors during live coding. | ||
| * Exit code improvements |
There was a problem hiding this comment.
Suggested change
| * Exit code improvements | |
| ### Automatically exit with exit code 0 | |
| If no issues were found or remain after fixing, both PHPCS and PHPCBF now exit with code 0. Users who prefer for non auto-fixables to be ignored for the exit code determination can now set the new ignore_non_auto_fixable_on_exit config flag to 1. | |
| For full details on the new exit codes, check the ["Advanced Usage"] Wiki page at (https://github.com/PHPCSStandards/PHP_CodeSniffer/wiki/Advanced-Usage#understanding-the-exit-codes). |
| * Less chance on scans failing on parse errors during live coding. | ||
| * Exit code improvements | ||
| * Proper separation of output between STDOUT and STDERR. | ||
| Piping output to STDOUT will no longer contain progress information or error notices |
There was a problem hiding this comment.
Suggested change
| Piping output to STDOUT will no longer contain progress information or error notices | |
| As per POSIX standards (https://en.wikipedia.org/wiki/Standard_streams#Standard_error_.28stderr.29), all status, debug, and progress output is now directed to STDERR instead of STDOUT. Only report output is now directed to STDOUT. Piping output to STDOUT will no longer contain progress information or error notices. As a result, timing and memory consumption stats will now be displayed more often. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR is intended to allow for conversation about the "press release"/mail to funders to accompany the PHP_CodeSniffer 4.0 release.
At this time, the text is just some draft notes to get the conversation started.