sdc-build-wp 4.1.0 → 4.1.2

package/vendor/wp-coding-standards/wpcs/WordPress/Docs/WP/DeprecatedParametersStandard.xml

@@ -1,40 +0,0 @@
-<?xml version="1.0"?>
-<documentation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    xsi:noNamespaceSchemaLocation="https://phpcsstandards.github.io/PHPCSDevTools/phpcsdocs.xsd"
-    title="Deprecated Function Parameters"
-    >
-    <standard>
-    <![CDATA[
-    Please refrain from passing deprecated WordPress function parameters.
-	In case, you need to pass an optional parameter positioned <em>after</em> the deprecated parameter, only ever pass the default value.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: not passing a deprecated parameter.">
-        <![CDATA[
-// First - and only - parameter deprecated.
-get_the_author();
-        ]]>
-        </code>
-        <code title="Invalid: passing a deprecated parameter.">
-        <![CDATA[
-// First - and only - parameter deprecated.
-get_the_author( <em>$string</em> );
-        ]]>
-        </code>
-    </code_comparison>
-    <code_comparison>
-        <code title="Valid: passing default value for a deprecated parameter.">
-        <![CDATA[
-// Third parameter deprecated in WP 2.3.0.
-add_option( 'option_name', 123, <em>''</em>, 'yes' );
-        ]]>
-        </code>
-        <code title="Invalid: not passing the default value for a deprecated parameter.">
-        <![CDATA[
-// Third parameter deprecated in WP 2.3.0.
-add_option( 'my_name', 123, <em>'oops'</em>, 'yes' );
-        ]]>
-        </code>
-    </code_comparison>
-</documentation>

package/vendor/wp-coding-standards/wpcs/WordPress/Docs/WP/EnqueuedResourceParametersStandard.xml

@@ -1,92 +0,0 @@
-<?xml version="1.0"?>
-<documentation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    xsi:noNamespaceSchemaLocation="https://phpcsstandards.github.io/PHPCSDevTools/phpcsdocs.xsd"
-    title="Enqueued Resource Parameters"
-    >
-    <standard>
-    <![CDATA[
-    The resource version must be set, to prevent the browser from using an outdated, cached version after the resource has been updated.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: Resource has a version number.">
-        <![CDATA[
-wp_register_style(
-    'someStyle-css',
-    $path_to_local_file,
-    array(),
-    <em>'1.0.0'</em>
-);
-        ]]>
-        </code>
-        <code title="Invalid: Resource has no version number set.">
-        <![CDATA[
-wp_register_style(
-    'someStyle-css',
-    $path_to_local_file,
-    array()
-);
-        ]]>
-        </code>
-    </code_comparison>
-    <standard>
-    <![CDATA[
-    The resource version must not be `false`. When this value is set to `false`, the WordPress Core version number will be used, which is incorrect for themes and plugins.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: Resource has a version number.">
-        <![CDATA[
-wp_enqueue_script(
-    'someScript-js',
-    $path_to_local_file,
-    array( 'jquery' ),
-    <em>'1.0.0'</em>,
-    true
-);
-        ]]>
-        </code>
-        <code title="Invalid: Resource has version set to false.">
-        <![CDATA[
-wp_enqueue_script(
-    'someScript-js',
-    $path_to_local_file,
-    array( 'jquery' ),
-    <em>false</em>,
-    true
-);
-        ]]>
-        </code>
-    </code_comparison>
-    <standard>
-    <![CDATA[
-    You must explicitly set a JavaScript resource to load in either the header or the footer of your page. It is recommended to load these resources in the footer by setting the `$in_footer` parameter to `true`.
-
-    Loading scripts in the header blocks parsing of the page and has a negative impact on load times. However, loading in the footer may break compatibility when other scripts rely on the resource to be available at any time.
-    In that case, you can pass `false` to make it explicit that the script should be loaded in the header of the page.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: The resource is specified to load in the footer.">
-        <![CDATA[
-wp_register_script(
-    'someScript-js',
-    $path_to_local_file,
-    array( 'jquery' ),
-    '1.0.0',
-    <em>true</em>
-);
-        ]]>
-        </code>
-        <code title="Invalid: The location to load this resource is not explicitly set.">
-        <![CDATA[
-wp_register_script(
-    'someScript-js',
-    $path_to_local_file,
-    array( 'jquery' ),
-    '1.0.0'
-);
-        ]]>
-        </code>
-    </code_comparison>
-</documentation>

package/vendor/wp-coding-standards/wpcs/WordPress/Docs/WP/EnqueuedResourcesStandard.xml

@@ -1,57 +0,0 @@
-<?xml version="1.0"?>
-<documentation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    xsi:noNamespaceSchemaLocation="https://phpcsstandards.github.io/PHPCSDevTools/phpcsdocs.xsd"
-    title="Enqueued Resources"
-    >
-    <standard>
-    <![CDATA[
-    Scripts must be registered/enqueued via wp_enqueue_script().
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: Script registered and enqueued correctly.">
-        <![CDATA[
-<em>wp_enqueue_script</em>( 
-    'someScript-js', 
-    $path_to_file, 
-    array( 'jquery' ),
-    '1.0.0',
-    true
-);
-        ]]>
-        </code>
-        <code title="Invalid: Script is directly embedded in HTML.">
-        <![CDATA[
-printf( 
-    '<em><script src="%s"></script></em>',
-    esc_url( $path_to_file )
-);
-        ]]>
-        </code>
-    </code_comparison>
-    <standard>
-    <![CDATA[
-    Stylesheets must be registered/enqueued via wp_enqueue_style().
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: Stylesheet registered and enqueued correctly.">
-        <![CDATA[
-<em>wp_enqueue_style</em>( 
-    'style-name', 
-    $path_to_file, 
-    array(), 
-    '1.0.0'
-);
-        ]]>
-        </code>
-        <code title="Invalid: Stylesheet is directly embedded in HTML.">
-        <![CDATA[
-printf( 
-    '<em><link rel="stylesheet" href="%s" /></em>',
-    esc_url( $path_to_file )
-);
-        ]]>
-        </code>
-    </code_comparison>
-</documentation>

package/vendor/wp-coding-standards/wpcs/WordPress/Docs/WP/PostsPerPageStandard.xml

@@ -1,73 +0,0 @@
-<?xml version="1.0"?>
-<documentation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    xsi:noNamespaceSchemaLocation="https://phpcsstandards.github.io/PHPCSDevTools/phpcsdocs.xsd"
-    title="High Posts Per Page Limit"
-    >
-    <standard>
-    <![CDATA[
-Using "posts_per_page" or "numberposts" with the value set to an high number opens up the potential for making requests slow if the query ends up querying thousands of posts.
-
-You should always fetch the lowest number possible that still gives you the number of results you find acceptable.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: posts_per_page is not over limit (default 100).">
-        <![CDATA[
-$args = array(
-    'posts_per_page' => <em>-1</em>,
-);
-$args = array(
-    'posts_per_page' => <em>100</em>,
-);
-$args = array(
-    'posts_per_page' => <em>'10'</em>,
-);
-
-$query_args['posts_per_page'] = <em>100</em>;
-
-_query_posts( 'nopaging=1&posts_per_page=<em>50</em>' );
-        ]]>
-        </code>
-        <code title="Invalid: posts_per_page is over limit (default 100).">
-        <![CDATA[
-$args = array(
-    'posts_per_page' => <em>101</em>,
-);
-
-$query_args['posts_per_page'] = <em>200</em>;
-
-_query_posts( 'nopaging=1&posts_per_page=<em>999</em>' );
-        ]]>
-        </code>
-    </code_comparison>
-    <code_comparison>
-        <code title="Valid: numberposts is not over limit (default 100).">
-        <![CDATA[
-$args = array(
-    'numberposts' => <em>-1</em>,
-);
-$args = array(
-    'numberposts' => <em>100</em>,
-);
-$args = array(
-    'numberposts' => <em>'10'</em>,
-);
-
-$query_args['numberposts'] = <em>'-1'<em>;
-
-_query_posts( 'numberposts=<em>50</em>' );
-        ]]>
-        </code>
-        <code title="Invalid: numberposts is over limit (default 100).">
-        <![CDATA[
-$args = array(
-    'numberposts' => <em>101</em>,
-);
-
-$query_args['numberposts'] = <em>'200'</em>;
-
-_query_posts( 'numberposts=<em>999</em>' );
-        ]]>
-        </code>
-    </code_comparison>
-</documentation>

package/vendor/wp-coding-standards/wpcs/WordPress/Docs/WhiteSpace/CastStructureSpacingStandard.xml

@@ -1,27 +0,0 @@
-<?xml version="1.0"?>
-<documentation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    xsi:noNamespaceSchemaLocation="https://phpcsstandards.github.io/PHPCSDevTools/phpcsdocs.xsd"
-    title="Cast Structure Spacing"
-    >
-    <standard>
-    <![CDATA[
-    A type cast should be preceded by whitespace.
-    There is only one exception to this rule: when the cast is preceded by the spread operator there should be no space between the spread operator and the cast.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: space before typecast.">
-        <![CDATA[
-$a =<em> </em>(int) '420';
-
-// No space between spread operator and cast.
-$a = function_call( <em>...(array)</em> $mixed );
-        ]]>
-        </code>
-        <code title="Invalid: no space before typecast.">
-        <![CDATA[
-$a <em>=(</em>int) '420';
-        ]]>
-        </code>
-    </code_comparison>
-</documentation>

package/vendor/wp-coding-standards/wpcs/WordPress/Docs/WhiteSpace/ControlStructureSpacingStandard.xml

@@ -1,150 +0,0 @@
-<?xml version="1.0"?>
-<documentation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    xsi:noNamespaceSchemaLocation="https://phpcsstandards.github.io/PHPCSDevTools/phpcsdocs.xsd"
-    title="Control Structure Spacing"
-    >
-    <standard>
-    <![CDATA[
-    Put one space on both sides of the opening and closing parentheses of control structures.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: One space on each side of the open and close parentheses.">
-        <![CDATA[
-while<em> ( </em>have_posts()<em> ) </em>{}
-
-// For multi-line conditions,
-// a new line is also accepted.
-if<em> ( </em>true === $condition
-    && $count > 10
-<em>) </em>{}
-        ]]>
-        </code>
-        <code title="Invalid: Incorrect spacing around the open and close parentheses.">
-        <![CDATA[
-// No spaces.
-while<em>(</em>have_posts()<em>)</em>{}
-
-// Too much space.
-while<em>   (   </em>have_posts()<em>   )   </em>{}
-        ]]>
-        </code>
-    </code_comparison>
-    <standard>
-    <![CDATA[
-    The open brace for the control structure must be on the same line as the close parenthesis or the control structure keyword, with one space between them.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: Open brace on the same line as the keyword/close parenthesis.">
-        <![CDATA[
-try<em> {</em>
-    // Do something.
-} catch (
-    ExceptionA | ExceptionB $e
-<em>) {</em>
-}
-        ]]>
-        </code>
-        <code title="Invalid: Open brace on a different line than the keyword/close parenthesis.">
-        <![CDATA[
-try
-<em>{</em>
-    // Do something.
-} catch ( Exception $e )
-<em>(</em>
-}
-        ]]>
-        </code>
-    </code_comparison>
-    <code_comparison>
-        <code title="Valid: One space between the keyword/close parenthesis and the open brace.">
-        <![CDATA[
-if ( $condition )<em> </em>{
-    // Do something.
-}
-        ]]>
-        </code>
-        <code title="Invalid: Too much space between the keyword/close parenthesis and the open brace.">
-        <![CDATA[
-if ( $condition )<em>     </em>{
-    // Do something.
-}
-        ]]>
-        </code>
-    </code_comparison>
-    <standard>
-    <![CDATA[
-    When using alternative control structure syntaxes, there should be one space between the close parenthesis and the colon opening the control structure body.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: One space before the colon.">
-        <![CDATA[
-foreach ( $types as $type )<em> </em>:
-    // Do something.
-endforeach;
-        ]]>
-        </code>
-        <code title="Invalid: No space before the colon.">
-        <![CDATA[
-foreach ( $types as $type )<em></em>:
-    // Do something.
-endforeach;
-        ]]>
-        </code>
-    </code_comparison>
-    <standard>
-    <![CDATA[
-    When a control structure is nested in another control structure and the closing braces follow each other, there should be no blank line between the closing braces.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: No blank line between the consecutive close braces.">
-        <![CDATA[
-if ( $a === $b ) {
-    if ( $something ) {
-        // Do something.
-    }
-}
-        ]]>
-        </code>
-        <code title="Invalid: Blank line(s) between the consecutive close braces.">
-        <![CDATA[
-if ( $a === $b ) {
-    if ( $something ) {
-        // Do something.
-    }<em>
-
-
-</em>}
-        ]]>
-        </code>
-    </code_comparison>
-    <standard>
-    <![CDATA[
-    [Optional, turned off by default]
-    There should be no blank line(s) at the start or end of the control structure body.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: No blank lines at the start or end of the control structure body.">
-        <![CDATA[
-if ( $a === $b ) {
-    echo $a;
-}
-        ]]>
-        </code>
-        <code title="Invalid: Blank line(s) at the start and end of the control structure body.">
-        <![CDATA[
-if ( $a === $b ) {
-<em>
-
-</em>    echo $a;
-<em>
-
-</em>}
-        ]]>
-        </code>
-    </code_comparison>
-</documentation>

package/vendor/wp-coding-standards/wpcs/WordPress/Docs/WhiteSpace/ObjectOperatorSpacingStandard.xml

@@ -1,19 +0,0 @@
-<documentation title="Object Operator Spacing">
-    <standard>
-    <![CDATA[
-    The object operators (->, ?->, ::) should not have any spaces around them, though new lines are allowed except for use with the `::class` constant.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: No spaces around the object operator.">
-        <![CDATA[
-$foo<em></em>-><em></em>bar();
-        ]]>
-        </code>
-        <code title="Invalid: Whitespace surrounding the object operator.">
-        <![CDATA[
-$foo<em>  </em>?-><em>  </em>bar();
-        ]]>
-        </code>
-    </code_comparison>
-</documentation>

package/vendor/wp-coding-standards/wpcs/WordPress/Docs/WhiteSpace/OperatorSpacingStandard.xml

@@ -1,61 +0,0 @@
-<?xml version="1.0"?>
-<documentation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    xsi:noNamespaceSchemaLocation="https://phpcsstandards.github.io/PHPCSDevTools/phpcsdocs.xsd"
-    title="Operator Spacing"
-    >
-    <standard>
-    <![CDATA[
-    Always put one space on both sides of logical, comparison and concatenation operators.
-    Always put one space after an assignment operator.
-    ]]>
-    </standard>
-    <code_comparison>
-        <code title="Valid: one space before and after an operator.">
-        <![CDATA[
-if ( $a<em> === </em>$b<em> && </em>$b<em> === </em>$c ) {}
-if (<em> ! </em>$var ) {}
-        ]]>
-        </code>
-        <code title="Invalid: too much/little space.">
-        <![CDATA[
-// Too much space.
-if ( $a === $b<em>   &&   </em>$b<em> ===      </em>$c ) {}
-if (<em>  ! </em>$var ) {}
-
-// Too little space.
-if ( $a<em>===</em>$b<em> &&</em>$b<em> ===</em>$c ) {}
-if (<em> !</em>$var ) {}
-        ]]>
-        </code>
-    </code_comparison>
-    <code_comparison>
-        <code title="Valid: a new line instead of a space is okay too.">
-        <![CDATA[
-if ( $a === $b<em>
-    && </em>$b === $c
-) {}
-        ]]>
-        </code>
-        <code title="Invalid: too much space after operator on new line.">
-        <![CDATA[
-if ( $a === $b<em>
-    &&     </em>$b === $c
-) {}
-        ]]>
-        </code>
-    </code_comparison>
-    <code_comparison>
-        <code title="Valid: one space after assignment operator.">
-        <![CDATA[
-$a   <em>= </em>'foo';
-$all <em>= </em>'foobar';
-        ]]>
-        </code>
-        <code title="Invalid: too much/little space after assignment operator.">
-        <![CDATA[
-$a   <em>=     </em>'foo';
-$all <em>=</em>'foobar';
-        ]]>
-        </code>
-    </code_comparison>
-</documentation>

package/vendor/wp-coding-standards/wpcs/WordPress/Helpers/ArrayWalkingFunctionsHelper.php

@@ -1,108 +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\Helpers;
-
-use PHP_CodeSniffer\Files\File;
-use PHPCSUtils\Utils\PassedParameters;
-
-/**
- * Helper functions and function lists for checking whether a function applies a callback to an array.
- *
- * @since 3.0.0 The property in this class was previously contained in the
- *              `WordPressCS\WordPress\Sniff` class and has been moved here.
- */
-final class ArrayWalkingFunctionsHelper {
-
-	/**
-	 * List of array functions which apply a callback to the array.
-	 *
-	 * These are often used for sanitization/escaping an array variable.
-	 *
-	 * Note: functions which alter the array by reference are not listed here on purpose.
-	 * These cannot easily be used for sanitization as they can't be combined with unslashing.
-	 * Similarly, they cannot be used for late escaping as the return value is a boolean, not
-	 * the altered array.
-	 *
-	 * @since 2.1.0
-	 * @since 3.0.0 - Moved from the Sniff class to this class.
-	 *              - Visibility changed from protected to private and property made static.
-	 *                Use the `get_functions()` method for access.
-	 *              - The value has changed from an integer to an array containing the integer
-	 *                parameter position + its name.
-	 *
-	 * @var array<string, array>
-	 */
-	private static $arrayWalkingFunctions = array(
-		'array_map' => array(
-			'position' => 1,
-			'name'     => 'callback',
-		),
-		'map_deep'  => array(
-			'position' => 2,
-			'name'     => 'callback',
-		),
-	);
-
-	/**
-	 * Retrieve a list of the supported "array walking" functions.
-	 *
-	 * @since 3.0.0
-	 *
-	 * @return array<string, bool>
-	 */
-	public static function get_functions() {
-		return \array_fill_keys( \array_keys( self::$arrayWalkingFunctions ), true );
-	}
-
-	/**
-	 * Check if a particular function is an "array walking" function.
-	 *
-	 * @since 3.0.0
-	 *
-	 * @param string $functionName The name of the function to check.
-	 *
-	 * @return bool
-	 */
-	public static function is_array_walking_function( $functionName ) {
-		return isset( self::$arrayWalkingFunctions[ strtolower( $functionName ) ] );
-	}
-
-	/**
-	 * Retrieve the parameter information for the callback parameter for an array walking function.
-	 *
-	 * @since 3.0.0
-	 *
-	 * @param \PHP_CodeSniffer\Files\File $phpcsFile The file where this token was found.
-	 * @param int                         $stackPtr  The position of function call name token.
-	 *
-	 * @return array|false Array with information on the callback parameter.
-	 *                     Or `FALSE` if the parameter is not found.
-	 *                     See the PHPCSUtils PassedParameters::getParameters() documentation
-	 *                     for the format of the returned (single-dimensional) array.
-	 */
-	public static function get_callback_parameter( File $phpcsFile, $stackPtr ) {
-		$tokens = $phpcsFile->getTokens();
-		if ( isset( $tokens[ $stackPtr ] ) === false ) {
-			return false;
-		}
-
-		$functionName = strtolower( $tokens[ $stackPtr ]['content'] );
-		if ( isset( self::$arrayWalkingFunctions[ $functionName ] ) === false ) {
-			return false;
-		}
-
-		return PassedParameters::getParameter(
-			$phpcsFile,
-			$stackPtr,
-			self::$arrayWalkingFunctions[ $functionName ]['position'],
-			self::$arrayWalkingFunctions[ $functionName ]['name']
-		);
-	}
-}