Gecko [ fernandoquevedodop.com ]

Name	Size	Permission
WordPress	[ DIR ]	drwxr-xr-x
WordPress-Core	[ DIR ]	drwxr-xr-x
WordPress-Docs	[ DIR ]	drwxr-xr-x
WordPress-Extra	[ DIR ]	drwxr-xr-x
CHANGELOG.md	182.56 KB	-rw-r--r--
LICENSE	1.07 KB	-rw-r--r--
README.md	14.91 KB	-rw-r--r--
_typos.toml	634 B	-rw-r--r--
composer.json	2.97 KB	-rw-r--r--
phpcs.xml.dist.sample	5.13 KB	-rw-r--r--

Code Editor : phpcs.xml.dist.sample

<?xml version="1.0"?>
<ruleset xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="Example Project" xsi:noNamespaceSchemaLocation="https://schema.phpcodesniffer.com/phpcs.xsd">

<description>A custom set of rules to check for a WPized WordPress project</description>

<exclude-pattern>/docroot/wp-admin/*</exclude-pattern>
	<exclude-pattern>/docroot/wp-includes/*</exclude-pattern>
	<exclude-pattern>/docroot/wp-*.php</exclude-pattern>
	<exclude-pattern>/docroot/index.php</exclude-pattern>
	<exclude-pattern>/docroot/xmlrpc.php</exclude-pattern>
	<exclude-pattern>/docroot/wp-content/plugins/*</exclude-pattern>

<exclude-pattern>/vendor/*</exclude-pattern>

<exclude-pattern>/node_modules/*</exclude-pattern>

<exclude-pattern>*.min.js</exclude-pattern>

<arg name="basepath" value="."/>

<arg name="parallel" value="8"/>

<rule ref="WordPress-Extra">
		<!--
		We may want a middle ground though. The best way to do this is add the
		entire ruleset, then rule by rule, remove ones that don't suit a project.
		We can do this by running `phpcs` with the '-s' flag, which allows us to
		see the names of the sniffs reporting errors.
		Once we know the sniff names, we can opt to exclude sniffs which don't
		suit our project like so.

The below two examples just show how you can exclude rules/error codes.
		They are not intended as advice about which sniffs to exclude.
		-->

</rule>

<rule ref="WordPress-Docs"/>

<rule ref="Generic.Commenting.Todo"/>

<!--
	To get the optimal benefits of using WordPressCS, we should add a couple of
	custom properties.
	Adjust the values of these properties to fit our needs.

For information on additional custom properties available, check out
	the wiki:
	https://github.com/WordPress/WordPress-Coding-Standards/wiki/Customizable-sniff-properties
	-->
	<config name="minimum_wp_version" value="6.0"/>

<!--
	Sometimes, you may want to exclude a certain directory, like your tests,
	for select sniffs.
	The below examples demonstrate how to do this.

In the example, the `GlobalVariablesOverride` rule is excluded for test files
	as it is sometimes necessary to overwrite WP globals in test situations (just
	don't forget to restore them after the test!).

Along the same lines, PHPUnit is getting stricter about using PSR-4 file names,
	so excluding test files from the `WordPress.Files.Filename` sniff can be a
	legitimate exclusion.

For more information on ruleset configuration options, check out the PHPCS wiki:
	https://github.com/PHPCSStandards/PHP_CodeSniffer/wiki/Annotated-Ruleset
	-->
	<rule ref="WordPress.WP.GlobalVariablesOverride">
		<exclude-pattern>/path/to/Tests/*Test\.php</exclude-pattern>
	</rule>
	<rule ref="WordPress.Files.FileName">
		<exclude-pattern>/path/to/Tests/*Test\.php</exclude-pattern>
	</rule>

</ruleset>

${this.title}

Code Editor : phpcs.xml.dist.sample