Eightshift coding standards for WordPress
MIT License
Bot releases are visible (Hide)
Helpers
is used. The Eightshift.Security.ComponentsEscape
sniff is updated and renamed to Eightshift.Security.HelpersEscape
to reflect this change.Published by goranalkovic-infinum about 1 year ago
Updated to WPCS v3.0.0
Still beta, as a fix that'll be in WPCS v3.1.0 is not out yet.
Thanks to @dingo-d for the update!
Published by dingo-d over 2 years ago
$allowedExtendedClasses
in the FunctionComment sniff
__invoke()
method.Published by dingo-d over 2 years ago
This release just fixes the CI/CD failures (xmllint and line width issue in one of the sniff file), no functional changes were made
Published by dingo-d over 2 years ago
overriddenClass
parameter for the EightShift ComponentsEscape sniff
Published by dingo-d over 2 years ago
WordPress.Security.EscapeOutput.OutputNotEscaped
sniff, because we are overloading itPublished by dingo-d over 2 years ago
Eightshift.Security.ComponentsEscape
sniff
Published by dingo-d over 2 years ago
use
statements.use
statements for everything else.Squiz.Commenting.FunctionComment
sniff which normally comes included via the WordPress-Docs
ruleset and makes an allowance for the __invoke
method in the CLI classes.Squiz
ruleset.WordPress.Security.EscapeOutput.OutputNotEscaped
sniff which comes included with WordPress-Extra
ruleset and makes an allowance for a certain EightshiftLibs\Helpers\Components
static methods (render
and outputCssVariables
).5
for scanning the EightShiftCS code itself as that code is run outside the context of WordPress.A huge thanks to Juliette Reinders Folmer (@jrfnl) for amazing help in fixing tons of issues with the ruleset and sniffs.
Published by dingo-d over 3 years ago
Published by dingo-d over 3 years ago
Components::render()
method from the eightshift-libsPublished by dingo-d almost 4 years ago
We renamed the package from infinum/coding-standards-wp
to infinum/eightshift-coding-standards
.
Published by dingo-d about 4 years ago
Published by dingo-d about 4 years ago
This is the official release of the Infinum coding standards for WordPress. It contains breaking changes, mostly in regard of the naming scheme.
To equate the way we write our PHP and JS we opted to follow a modified PSR standards.
What this means is that we will remove liberal spacing, add some PSR12 modifications regarding arguments placing in closures, change snake_case with CamelCase for classes (for autoload puropses) and some other minor changes that will be documented below.
If you wish to use the old standards, be sure to modify your projects composer.json
file with the appropriate version.
Published by dingo-d over 4 years ago
WordPressCS\WordPress
in the DisallowedShortcodeSniff
Published by dingo-d over 4 years ago
-
pattern in files in sectionsPublished by dingo-d almost 6 years ago
WordPress
rulesetWordPress.Arrays.ArrayIndentation
to avoid it clashing with Generic indentation sniffPublished by dingo-d almost 6 years ago
This is a big update to the Infinum's coding standards for WordPress. A lot of things were fixed and changed as listed in the changelog:
Published by dingo-d about 6 years ago
Force WPCS dependency to be greater or equal to 1.0.0
Published by dingo-d about 6 years ago
This update is made after the release of WPCS 1.0.0 version.
Changes:
Generic.CodeAnalysis.UnusedFunctionParameter
WordPress-VIP
ruleset as it's deprecatedPostsPerPage
rule from VIP to WP namespaceDirectDatabaseQuery
from VIP to WP namespace, and YodaConditions
as wellDOMDocument
exclusions from ruleset, as it is project specific and can be added per projectPublished by dingo-d over 6 years ago
Updated array indentation to respect 2 spaces instead of 4 when indenting array keys.