Some PHPCS Updates

Author: bd-viget

.phpcs.xml

@@ -1,5 +1,5 @@
 <?xml version="1.0"?>
-<ruleset xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="Example Project" xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/PHPCSStandards/PHP_CodeSniffer/master/phpcs.xsd">
+<ruleset xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="Viget Blocks Toolkit" xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/PHPCSStandards/PHP_CodeSniffer/master/phpcs.xsd">
 
     <description>A custom set of rules to check for a WPized WordPress project</description>
 
@@ -42,24 +42,15 @@
     #############################################################################
     -->
 
+    <rule ref="WordPress">
+        <exclude name="Generic.Arrays.DisallowShortArraySyntax"/>
+        <exclude name="Universal.Arrays.DisallowShortArraySyntax"/>
+    </rule>
+
     <!-- Include the WordPress-Extra standard. -->
     <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.
-        -->
-
-        <!--
-        <exclude name="WordPress.WhiteSpace.ControlStructureSpacing"/>
-        <exclude name="Modernize.FunctionCalls.Dirname.Nested"/>
-        -->
+        <exclude name="Generic.Arrays.DisallowShortArraySyntax"/>
+        <exclude name="Universal.Arrays.DisallowShortArraySyntax"/>
     </rule>
 
     <!-- Let's also check that everything is properly documented. -->
@@ -105,16 +96,17 @@
     <rule ref="WordPress.WP.I18n">
         <properties>
             <property name="text_domain" type="array">
-                <element value="wp-starter"/>
-                <element value="library-wp-starter"/>
+                <element value="viget-blocks-toolkit"/>
             </property>
         </properties>
     </rule>
 
     <rule ref="WordPress.NamingConventions.PrefixAllGlobals">
         <properties>
             <property name="prefixes" type="array">
-                <element value="wpstarter_"/>
+                <element value="VGTBT_"/>
+                <element value="vgtbt_"/>
+                <element value="VigetBlocksToolkit"/>
             </property>
         </properties>
     </rule>

includes/parts-kit.php

@@ -8,7 +8,7 @@
 use Viget\VigetBlocksToolkit\Block_Registration;
 
 add_filter(
-	'viget_parts_kit_block_%',
+	'vgtpk_parts_kit_block_%',
 	function ( string $output, string $block_name ): string {
 		$block = Block_Registration::get_block( $block_name );
 
@@ -19,7 +19,7 @@ function ( string $output, string $block_name ): string {
 		if ( ! empty( $block['path'] ) ) {
 			$include = $block['path'] . '/block.php';
 
-			// Autoload block.php within block directory
+			// Autoload block.php within block directory.
 			if ( file_exists( $include ) ) {
 				require_once $include;
 			}
@@ -39,12 +39,12 @@ function ( string $output, string $block_name ): string {
  * @return string
  */
 function vgtbt_parse_inner_blocks( string $output ): string {
-	// Check if InnerBlocks tag has a template attribute with regular expression
+	// Check if InnerBlocks tag has a template attribute with regular expression.
 	if ( ! preg_match( '/<InnerBlocks[^>]*template="([^"]*)"[^>]*>/i', $output, $matches ) ) {
 		return $output;
 	}
 
-	// Get the template attribute value
+	// Get the template attribute value.
 	$template = $matches[1];
 	$template = htmlspecialchars_decode( $template );
 	$template = json_decode( $template, true );