Add ability to whitelist specific functions to the `AbstractFunctionR…

…estrictions` class.

This is only useful when used in combination with blocking a function group using a wildcard in the function name.

However, it does make it more forward compatible. This allows to still block a complete (PHP) extension , even for new functions being added to the extension, while whitelisting - for instance - a WP native function which was named a bit unfortunately.

WordPress/AbstractFunctionRestrictionsSniff.php

@@ -165,6 +165,10 @@ public function process( PHP_CodeSniffer_File $phpcsFile, $stackPtr ) {
 				continue;
 			}
 
+			if ( isset( $group['whitelist'][ $token['content'] ] ) ) {
+				continue;
+			}
+
 			if ( preg_match( $group['regex'], $token['content'] ) < 1 ) {
 				continue;
 			}

WordPress/Sniffs/DB/RestrictedFunctionsSniff.php

@@ -51,6 +51,9 @@ public function getGroups() {
 					'mysqlnd_memcache_*',
 					'maxdb_*',
 				),
+				'whitelist' => array(
+					'mysql_to_rfc3339' => true,
+				),
 			),
 
 		);

WordPress/Tests/DB/RestrictedFunctionsUnitTest.inc

@@ -74,3 +74,17 @@ maxdb_num_fields();
 maxdb_prepare();
 maxdb_real_query
 maxdb_stat();
+
+
+/**
+ * And these shouldn't give an error.
+ */
+
+// WP Native function which was named a bit unfortunately.
+mysql_to_rfc3339(); // Ok.
+
+// Other WP Native functions which shouldn't give a problem anyway.
+mysql2date(); // Ok.
+wp_check_mysql_version(); // Ok.
+wp_check_php_mysql_version(); // Ok.
+WP_Date_Query::build_mysql_datetime(); // Ok.