sdc-build-wp 4.1.0 → 4.1.2

package/vendor/wp-coding-standards/wpcs/LICENSE

@@ -1,21 +0,0 @@
-The MIT License (MIT)
-
-Copyright (c) 2009 John Godley and contributors.
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.

package/vendor/wp-coding-standards/wpcs/README.md

@@ -1,261 +0,0 @@
-<div aria-hidden="true">
-
-[![Latest Stable Version](https://poser.pugx.org/wp-coding-standards/wpcs/v/stable)](https://packagist.org/packages/wp-coding-standards/wpcs)
-[![Release Date of the Latest Version](https://img.shields.io/github/release-date/WordPress/WordPress-Coding-Standards.svg?maxAge=1800)](https://github.com/WordPress/WordPress-Coding-Standards/releases)
-:construction:
-[![Latest Unstable Version](https://img.shields.io/badge/unstable-dev--develop-e68718.svg?maxAge=2419200)](https://packagist.org/packages/wp-coding-standards/wpcs#dev-develop)
-
-[![Basic QA checks](https://github.com/WordPress/WordPress-Coding-Standards/actions/workflows/basic-qa.yml/badge.svg)](https://github.com/WordPress/WordPress-Coding-Standards/actions/workflows/basic-qa.yml)
-[![Unit Tests](https://github.com/WordPress/WordPress-Coding-Standards/actions/workflows/unit-tests.yml/badge.svg)](https://github.com/WordPress/WordPress-Coding-Standards/actions/workflows/unit-tests.yml)
-[![codecov.io](https://codecov.io/gh/WordPress/WordPress-Coding-Standards/graph/badge.svg?token=UzFYn0RzVG&branch=develop)](https://codecov.io/gh/WordPress/WordPress-Coding-Standards?branch=develop)
-
-[![Minimum PHP Version](https://img.shields.io/packagist/php-v/wp-coding-standards/wpcs.svg?maxAge=3600)](https://packagist.org/packages/wp-coding-standards/wpcs)
-[![Tested on PHP 5.4 to 8.3](https://img.shields.io/badge/tested%20on-PHP%205.4%20|%205.5%20|%205.6%20|%207.0%20|%207.1%20|%207.2%20|%207.3%20|%207.4%20|%208.0%20|%208.1%20|%208.2%20|%208.3-green.svg?maxAge=2419200)](https://github.com/WordPress/WordPress-Coding-Standards/actions/workflows/unit-tests.yml)
-
-[![License: MIT](https://poser.pugx.org/wp-coding-standards/wpcs/license)](https://github.com/WordPress/WordPress-Coding-Standards/blob/develop/LICENSE)
-[![Total Downloads](https://poser.pugx.org/wp-coding-standards/wpcs/downloads)](https://packagist.org/packages/wp-coding-standards/wpcs/stats)
-
-</div>
-
-
-# WordPress Coding Standards for PHP_CodeSniffer
-
-* [Introduction](#introduction)
-* [Minimum Requirements](#minimum-requirements)
-* [Installation](#installation)
-    + [Composer Project-based Installation](#composer-project-based-installation)
-    + [Composer Global Installation](#composer-global-installation)
-    + [Updating your WordPressCS install to a newer version](#updating-your-wordpresscs-install-to-a-newer-version)
-    + [Using your WordPressCS install](#using-your-wordpresscs-install)
-* [Rulesets](#rulesets)
-    + [Standards subsets](#standards-subsets)
-    + [Using a custom ruleset](#using-a-custom-ruleset)
-    + [Customizing sniff behaviour](#customizing-sniff-behaviour)
-    + [Recommended additional rulesets](#recommended-additional-rulesets)
-* [How to use](#how-to-use)
-    + [Command line](#command-line)
-    + [Using PHPCS and WordPressCS from within your IDE](#using-phpcs-and-wordpresscs-from-within-your-ide)
-* [Running your code through WordPressCS automatically using Continuous Integration tools](#running-your-code-through-wordpresscs-automatically-using-continuous-integration-tools)
-* [Fixing errors or ignoring them](#fixing-errors-or-ignoring-them)
-    + [Tools shipped with WordPressCS](#tools-shipped-with-wordpresscs)
-* [Contributing](#contributing)
-* [Funding](#funding)
-* [License](#license)
-
----
-
-## Introduction
-
-This project is a collection of [PHP_CodeSniffer](https://github.com/PHPCSStandards/PHP_CodeSniffer) rules (sniffs) to validate code developed for WordPress. It ensures code quality and adherence to coding conventions, especially the official [WordPress Coding Standards](https://make.wordpress.org/core/handbook/best-practices/coding-standards/).
-
-This project needs funding. [Find out how you can help](#funding).
-
-## Minimum Requirements
-
-The WordPress Coding Standards package requires:
-* PHP 5.4 or higher with the following extensions enabled:
-    - [Filter](https://www.php.net/book.filter)
-    - [libxml](https://www.php.net/book.libxml)
-    - [Tokenizer](https://www.php.net/book.tokenizer)
-    - [XMLReader](https://www.php.net/book.xmlreader)
-* [Composer](https://getcomposer.org/)
-
-For the best results, it is recommended to also ensure the following additional PHP extensions are enabled:
-- [iconv](https://www.php.net/book.iconv)
-- [Multibyte String](https://www.php.net/book.mbstring)
-
-## Installation
-
-As of [WordPressCS 3.0.0](https://make.wordpress.org/core/2023/08/21/wordpresscs-3-0-0-is-now-available/), installation via Composer using the below instructions is the only supported type of installation.
-
-[Composer](https://getcomposer.org/) will automatically install the project dependencies and register the rulesets from WordPressCS and other external standards with PHP_CodeSniffer using the [Composer PHPCS plugin](https://github.com/PHPCSStandards/composer-installer).
-
-> If you are upgrading from an older WordPressCS version to version 3.0.0, please read the [Upgrade guide for ruleset maintainers and end-users](https://github.com/WordPress/WordPress-Coding-Standards/wiki/Upgrade-Guide-to-WordPressCS-3.0.0-for-ruleset-maintainers) first!
-
-### Composer Project-based Installation
-
-Run the following from the root of your project:
-```bash
-composer config allow-plugins.dealerdirect/phpcodesniffer-composer-installer true
-composer require --dev wp-coding-standards/wpcs:"^3.0"
-```
-
-### Composer Global Installation
-
-Alternatively, you may want to install this standard globally:
-```bash
-composer global config allow-plugins.dealerdirect/phpcodesniffer-composer-installer true
-composer global require --dev wp-coding-standards/wpcs:"^3.0"
-```
-
-### Updating your WordPressCS install to a newer version
-
-If you installed WordPressCS using either of the above commands, you can upgrade to a newer version as follows:
-```bash
-# Project local install
-composer update wp-coding-standards/wpcs --with-dependencies
-
-# Global install
-composer global update wp-coding-standards/wpcs --with-dependencies
-```
-
-### Using your WordPressCS install
-
-Once you have installed WordPressCS using either of the above commands, use it as follows:
-```bash
-# Project local install
-vendor/bin/phpcs -ps . --standard=WordPress
-
-# Global install
-%USER_DIRECTORY%/Composer/vendor/bin/phpcs -ps . --standard=WordPress
-```
-
-> **Pro-tip**: For the convenience of using `phpcs` as a global command, use the _Global install_ method and add the path to the `%USER_DIRECTORY%/Composer/vendor/bin` directory to the `PATH` environment variable for your operating system.
-
-
-##  Rulesets
-
-### Standards subsets
-
-The project encompasses a super-set of the sniffs that the WordPress community may need. If you use the `WordPress` standard you will get all the checks.
-
-You can use the following as standard names when invoking `phpcs` to select sniffs, fitting your needs:
-
-* `WordPress` - complete set with all of the sniffs in the project
-  - `WordPress-Core` - main ruleset for [WordPress core coding standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/php/)
-  - `WordPress-Docs` - additional ruleset for [WordPress inline documentation standards](https://developer.wordpress.org/coding-standards/inline-documentation-standards/php/)
-  - `WordPress-Extra` - extended ruleset with recommended best practices, not sufficiently covered in the WordPress core coding standards
-    - includes `WordPress-Core`
-
-### Using a custom ruleset
-
-If you need to further customize the selection of sniffs for your project - you can create a custom ruleset file.
-
-When you name this file either `.phpcs.xml`, `phpcs.xml`, `.phpcs.xml.dist` or `phpcs.xml.dist`, PHP_CodeSniffer will automatically locate it as long as it is placed in the directory from which you run the CodeSniffer or in a directory above it. If you follow these naming conventions you don't have to supply a `--standard` CLI argument.
-
-For more info, read about [using a default configuration file](https://github.com/PHPCSStandards/PHP_CodeSniffer/wiki/Advanced-Usage#using-a-default-configuration-file). See also the provided WordPressCS [`phpcs.xml.dist.sample`](phpcs.xml.dist.sample) file and the [fully annotated example ruleset](https://github.com/PHPCSStandards/PHP_CodeSniffer/wiki/Annotated-ruleset.xml) in the PHP_CodeSniffer documentation.
-
-### Customizing sniff behaviour
-
-The WordPress Coding Standard contains a number of sniffs which are configurable. This means that you can turn parts of the sniff on or off, or change the behaviour by setting a property for the sniff in your custom `[.]phpcs.xml[.dist]` file.
-
-You can find a complete list of all the properties you can change for the WordPressCS sniffs in the [wiki](https://github.com/WordPress/WordPress-Coding-Standards/wiki/Customizable-sniff-properties).
-
-WordPressCS also uses sniffs from PHPCSExtra and from PHP_CodeSniffer itself.
-The [README for PHPCSExtra](https://github.com/PHPCSStandards/PHPCSExtra) contains information on the properties which can be set for the sniff from PHPCSExtra.
-Information on custom properties which can be set for sniffs from PHP_CodeSniffer can be found in the [PHP_CodeSniffer wiki](https://github.com/PHPCSStandards/PHP_CodeSniffer/wiki/Customisable-Sniff-Properties).
-
-
-### Recommended additional rulesets
-
-#### PHPCompatibility
-
-The [PHPCompatibility](https://github.com/PHPCompatibility/PHPCompatibility) ruleset and its subset [PHPCompatibilityWP](https://github.com/PHPCompatibility/PHPCompatibilityWP) come highly recommended.
-The [PHPCompatibility](https://github.com/PHPCompatibility/PHPCompatibility) sniffs are designed to analyse your code for cross-version PHP compatibility.
-
-The [PHPCompatibilityWP](https://github.com/PHPCompatibility/PHPCompatibilityWP) ruleset is based on PHPCompatibility, but specifically crafted to prevent false positives for projects which expect to run within the context of WordPress, i.e. core, plugins and themes.
-
-Install either as a separate ruleset and run it separately against your code or add it to your custom ruleset, like so:
-```xml
-<config name="testVersion" value="7.0-"/>
-<rule ref="PHPCompatibilityWP">
-    <include-pattern>*\.php$</include-pattern>
-</rule>
-```
-
-Whichever way you run it, do make sure you set the `testVersion` to run the sniffs against. The `testVersion` determines for which PHP versions you will receive compatibility information. The recommended setting for this at this moment is  `7.0-` to support the same PHP versions as WordPress Core supports.
-
-For more information about setting the `testVersion`, see:
-* [PHPCompatibility: Sniffing your code for compatibility with specific PHP version(s)](https://github.com/PHPCompatibility/PHPCompatibility#sniffing-your-code-for-compatibility-with-specific-php-versions)
-* [PHPCompatibility: Using a custom ruleset](https://github.com/PHPCompatibility/PHPCompatibility#using-a-custom-ruleset)
-
-#### VariableAnalysis
-
-For some additional checks around (undefined/unused) variables, the [`VariableAnalysis`](https://github.com/sirbrillig/phpcs-variable-analysis/) standard is a handy addition.
-
-#### VIP Coding Standards
-
-For those projects which deploy to the WordPress VIP platform, it is recommended to also use the [official WordPress VIP coding standards](https://github.com/Automattic/VIP-Coding-Standards) ruleset.
-
-
-## How to use
-
-### Command line
-
-Run the `phpcs` command line tool on a given file or directory, for example:
-```bash
-vendor/bin/phpcs --standard=WordPress wp-load.php
-```
-
-Will result in following output:
-```
---------------------------------------------------------------------------------
-FOUND 6 ERRORS AND 4 WARNINGS AFFECTING 5 LINES
---------------------------------------------------------------------------------
-  36 | WARNING | error_reporting() can lead to full path disclosure.
-  36 | WARNING | error_reporting() found. Changing configuration values at
-     |         | runtime is strongly discouraged.
-  52 | WARNING | Silencing errors is strongly discouraged. Use proper error
-     |         | checking instead. Found: @file_exists( dirname(...
-  52 | WARNING | Silencing errors is strongly discouraged. Use proper error
-     |         | checking instead. Found: @file_exists( dirname(...
-  75 | ERROR   | Overriding WordPress globals is prohibited. Found assignment
-     |         | to $path
-  78 | ERROR   | Detected usage of a possibly undefined superglobal array
-     |         | index: $_SERVER['REQUEST_URI']. Use isset() or empty() to
-     |         | check the index exists before using it
-  78 | ERROR   | $_SERVER['REQUEST_URI'] not unslashed before sanitization. Use
-     |         | wp_unslash() or similar
-  78 | ERROR   | Detected usage of a non-sanitized input variable:
-     |         | $_SERVER['REQUEST_URI']
- 104 | ERROR   | All output should be run through an escaping function (see the
-     |         | Security sections in the WordPress Developer Handbooks), found
-     |         | '$die'.
- 104 | ERROR   | All output should be run through an escaping function (see the
-     |         | Security sections in the WordPress Developer Handbooks), found
-     |         | '__'.
---------------------------------------------------------------------------------
-```
-
-### Using PHPCS and WordPressCS from within your IDE
-
-The [wiki](https://github.com/WordPress/WordPress-Coding-Standards/wiki) contains links to various in- and external tutorials about setting up WordPressCS to work in your IDE.
-
-
-## Running your code through WordPressCS automatically using Continuous Integration tools
-
-- [Running in GitHub Actions](https://github.com/WordPress/WordPress-Coding-Standards/wiki/Running-in-GitHub-Actions)
-- [Running in Travis](https://github.com/WordPress/WordPress-Coding-Standards/wiki/Running-in-Travis)
-
-
-## Fixing errors or ignoring them
-
-You can find information on how to deal with some of the more frequent issues in the [wiki](https://github.com/WordPress/WordPress-Coding-Standards/wiki).
-
-### Tools shipped with WordPressCS
-
-Since version 1.2.0, WordPressCS has a special sniff category `Utils`.
-
-This sniff category contains some tools which, generally speaking, will only be needed to be run once over a codebase and for which the fixers can be considered _risky_, i.e. very careful review by a developer is needed before accepting the fixes made by these sniffs.
-
-The sniffs in this category are disabled by default and can only be activated by adding some properties for each sniff via a custom ruleset.
-
-At this moment, WordPressCS offer the following tools:
-* `WordPress.Utils.I18nTextDomainFixer` - This sniff can replace the text domain used in a code-base.
-    The sniff will fix the text domains in both I18n function calls as well as in a plugin/theme header.
-    Passing the following properties will activate the sniff:
-    - `old_text_domain`: an array with one or more (old) text domain names which need to be replaced;
-    - `new_text_domain`: the correct (new) text domain as a string.
-
-
-## Contributing
-
-See [CONTRIBUTING](.github/CONTRIBUTING.md), including information about [unit testing](.github/CONTRIBUTING.md#unit-testing) the standard.
-
-## Funding
-
-If you want to sponsor the work on WordPressCS, you can do so by donating to the [PHP_CodeSniffer Open Collective](https://opencollective.com/php_codesniffer).
-
-## License
-
-See [LICENSE](LICENSE) (MIT).

package/vendor/wp-coding-standards/wpcs/WordPress/AbstractArrayAssignmentRestrictionsSniff.php

@@ -1,261 +0,0 @@
-<?php
-/**
- * WordPress Coding Standard.
- *
- * @package WPCS\WordPressCodingStandards
- * @link    https://github.com/WordPress/WordPress-Coding-Standards
- * @license https://opensource.org/licenses/MIT MIT
- */
-
-namespace WordPressCS\WordPress;
-
-use PHP_CodeSniffer\Util\Tokens;
-use PHPCSUtils\BackCompat\BCFile;
-use PHPCSUtils\Utils\GetTokensAsString;
-use PHPCSUtils\Utils\MessageHelper;
-use PHPCSUtils\Utils\TextStrings;
-use WordPressCS\WordPress\Helpers\RulesetPropertyHelper;
-use WordPressCS\WordPress\Sniff;
-
-/**
- * Restricts array assignment of certain keys.
- *
- * @since 0.3.0
- * @since 0.10.0 Class became a proper abstract class. This was already the behaviour.
- *               Moved the file and renamed the class from
- *               `\WordPressCS\WordPress\Sniffs\Arrays\ArrayAssignmentRestrictionsSniff` to
- *               `\WordPressCS\WordPress\AbstractArrayAssignmentRestrictionsSniff`.
- */
-abstract class AbstractArrayAssignmentRestrictionsSniff extends Sniff {
-
-	/**
-	 * Exclude groups.
-	 *
-	 * Example: 'foo,bar'
-	 *
-	 * @since 0.3.0
-	 * @since 1.0.0 This property now expects to be passed an array.
-	 *              Previously a comma-delimited string was expected.
-	 *
-	 * @var string[]
-	 */
-	public $exclude = array();
-
-	/**
-	 * Groups of variable data to check against.
-	 * Don't use this in extended classes, override getGroups() instead.
-	 * This is only used for Unit tests.
-	 *
-	 * @var array<string, array>
-	 */
-	public static $groups = array();
-
-	/**
-	 * Cache for the excluded groups information.
-	 *
-	 * @since 0.11.0
-	 *
-	 * @var array<string, bool>
-	 */
-	protected $excluded_groups = array();
-
-	/**
-	 * Cache for the group information.
-	 *
-	 * @since 0.13.0
-	 *
-	 * @var array<string, array>
-	 */
-	protected $groups_cache = array();
-
-	/**
-	 * Returns an array of tokens this test wants to listen for.
-	 *
-	 * @return array
-	 */
-	public function register() {
-		// Retrieve the groups only once and don't set up a listener if there are no groups.
-		if ( false === $this->setup_groups() ) {
-			return array();
-		}
-
-		return array(
-			\T_DOUBLE_ARROW,
-			\T_CLOSE_SQUARE_BRACKET,
-			\T_CONSTANT_ENCAPSED_STRING,
-			\T_DOUBLE_QUOTED_STRING,
-		);
-	}
-
-	/**
-	 * Groups of variables to restrict.
-	 *
-	 * This method should be overridden in extending classes.
-	 *
-	 * Example: groups => array(
-	 *  'groupname' => array(
-	 *      'type'    => 'error' | 'warning',
-	 *      'message' => 'Descriptive error message. The error message will be passed the $key and $val of the current array assignment.',
-	 *      'keys'    => array( 'key1', 'another_key' ),
-	 *  )
-	 * )
-	 *
-	 * @return array<string, array>
-	 */
-	abstract public function getGroups();
-
-	/**
-	 * Cache the groups.
-	 *
-	 * @since 0.13.0
-	 *
-	 * @return bool True if the groups were setup. False if not.
-	 */
-	protected function setup_groups() {
-		$this->groups_cache = $this->getGroups();
-
-		if ( empty( $this->groups_cache ) && empty( self::$groups ) ) {
-			return false;
-		}
-
-		// Allow for adding extra unit tests.
-		if ( ! empty( self::$groups ) ) {
-			$this->groups_cache = array_merge( $this->groups_cache, self::$groups );
-		}
-
-		return true;
-	}
-
-	/**
-	 * Processes this test, when one of its tokens is encountered.
-	 *
-	 * @param int $stackPtr The position of the current token in the stack.
-	 *
-	 * @return void
-	 */
-	public function process_token( $stackPtr ) {
-
-		$this->excluded_groups = RulesetPropertyHelper::merge_custom_array( $this->exclude );
-		if ( array_diff_key( $this->groups_cache, $this->excluded_groups ) === array() ) {
-			// All groups have been excluded.
-			// Don't remove the listener as the exclude property can be changed inline.
-			return;
-		}
-
-		$token = $this->tokens[ $stackPtr ];
-
-		if ( \T_CLOSE_SQUARE_BRACKET === $token['code'] ) {
-			$equalPtr = $this->phpcsFile->findNext( Tokens::$emptyTokens, ( $stackPtr + 1 ), null, true );
-			if ( \T_EQUAL !== $this->tokens[ $equalPtr ]['code']
-				&& \T_COALESCE_EQUAL !== $this->tokens[ $equalPtr ]['code']
-			) {
-				// This is not an assignment. Bow out.
-				return;
-			}
-		}
-
-		// Instances: Multi-dimensional array.
-		$inst = array();
-
-		/*
-		 * Covers array assignments:
-		 * `$foo = array( 'bar' => 'taz' );`
-		 * `$foo['bar'] = $taz;`
-		 */
-		if ( \T_CLOSE_SQUARE_BRACKET === $token['code'] || \T_DOUBLE_ARROW === $token['code'] ) {
-			$operator = $stackPtr; // T_DOUBLE_ARROW.
-			if ( \T_CLOSE_SQUARE_BRACKET === $token['code'] ) {
-				$operator = $equalPtr;
-			}
-
-			$keyIdx = $this->phpcsFile->findPrevious( Tokens::$emptyTokens, ( $stackPtr - 1 ), null, true );
-			if ( isset( Tokens::$stringTokens[ $this->tokens[ $keyIdx ]['code'] ] )
-				&& ! is_numeric( $this->tokens[ $keyIdx ]['content'] )
-			) {
-				$key      = TextStrings::stripQuotes( $this->tokens[ $keyIdx ]['content'] );
-				$valStart = $this->phpcsFile->findNext( Tokens::$emptyTokens, ( $operator + 1 ), null, true );
-				$valEnd   = BCFile::findEndOfStatement( $this->phpcsFile, $valStart, \T_COLON );
-				if ( \T_COMMA === $this->tokens[ $valEnd ]['code']
-					|| \T_SEMICOLON === $this->tokens[ $valEnd ]['code']
-				) {
-					// FindEndOfStatement includes the comma/semi-colon if that's the end of the statement.
-					// That's not what we want (and inconsistent), so remove it.
-					--$valEnd;
-				}
-
-				$val          = trim( GetTokensAsString::compact( $this->phpcsFile, $valStart, $valEnd, true ) );
-				$inst[ $key ] = array(
-					'value'  => $val,
-					'line'   => $token['line'],
-					'keyptr' => $keyIdx,
-				);
-			}
-		} elseif ( isset( Tokens::$stringTokens[ $token['code'] ] ) ) {
-			/*
-			 * Covers assignments via query parameters: `$foo = 'bar=taz&other=thing';`.
-			 */
-			if ( preg_match_all( '#(?:^|&)([a-z_]+)=([^&]*)#i', TextStrings::stripQuotes( $token['content'] ), $matches ) <= 0 ) {
-				return; // No assignments here, nothing to check.
-			}
-
-			foreach ( $matches[1] as $match_nr => $key ) {
-				$inst[ $key ] = array(
-					'value'  => $matches[2][ $match_nr ],
-					'line'   => $token['line'],
-					'keyptr' => $stackPtr,
-				);
-			}
-		}
-
-		if ( empty( $inst ) ) {
-			return;
-		}
-
-		foreach ( $this->groups_cache as $groupName => $group ) {
-
-			if ( isset( $this->excluded_groups[ $groupName ] ) ) {
-				continue;
-			}
-
-			foreach ( $inst as $key => $assignment ) {
-				if ( ! \in_array( $key, $group['keys'], true ) ) {
-					continue;
-				}
-
-				$output = \call_user_func( array( $this, 'callback' ), $key, $assignment['value'], $assignment['line'], $group );
-
-				if ( ! isset( $output ) || false === $output ) {
-					continue;
-				} elseif ( true === $output ) {
-					$message = $group['message'];
-				} else {
-					$message = $output;
-				}
-
-				MessageHelper::addMessage(
-					$this->phpcsFile,
-					$message,
-					$assignment['keyptr'],
-					( 'error' === $group['type'] ),
-					MessageHelper::stringToErrorcode( $groupName . '_' . $key ),
-					array( $key, $assignment['value'] )
-				);
-			}
-		}
-	}
-
-	/**
-	 * Callback to process each confirmed key, to check value.
-	 *
-	 * This method must be extended to add the logic to check assignment value.
-	 *
-	 * @param string $key   Array index / key.
-	 * @param mixed  $val   Assigned value.
-	 * @param int    $line  Token line.
-	 * @param array  $group Group definition.
-	 *
-	 * @return mixed FALSE if no match, TRUE if matches, STRING if matches
-	 *               with custom error message passed to ->process().
-	 */
-	abstract public function callback( $key, $val, $line, $group );
-}