#45956 closed task (blessed) (fixed)
Upgrade WPCS to 1.2.1
Reported by: | pento | Owned by: | pento |
---|---|---|---|
Milestone: | 5.1 | Priority: | normal |
Severity: | normal | Version: | |
Component: | General | Keywords: | |
Focuses: | coding-standards | Cc: |
Description (last modified by )
By upgrading WPCS to 1.2.1:
Generic.PHP.NoSilencedErrors.Discouraged
is replaced byWordPress.PHP.NoSilencedErrors.Discouraged
, which whitelists 123 instances of errors being appropriately silenced.- Autofix 191 violations of
Generic.WhiteSpace.ScopeIndent
. - Fix 6 false positives in
WordPress.WhiteSpace.PrecisionAlignment.Found
. - The
allowMultipleArguments
property ofPEAR.Functions.FunctionCallSignature
defaults tofalse
, so we can remove that custom setting fromphpcs.xml.dist
.
By upgrading PHPCS to 3.4.1:
- Fix 23 false positives in
Squiz.PHP.DisallowMultipleAssignments.Found
Attachments (1)
Change History (4)
#3
@
6 years ago
Just FYI: PHPCS 3.4.1 is not (yet) released. The latest released version is 3.4.0.
On another note, WPCS 2.0.0 is expected to be released within the week.
Upgrading will involve updating some of the error codes used in the inline whitelist comments (mostly those just added for variabe names) as well as in the ruleset.
I expect the upgrade will throw only a few new errors, all of which I expect to be auto-fixable (for typecasts).
For more information, see the changelog of the WPCS 2.0.0-RC1 release.
Note: See
TracTickets for help on using
tickets.
In 44574: