Changeset 56382 for trunk/src/wp-includes/block-supports/settings.php

Timestamp:

08/10/2023 04:47:00 PM (13 months ago)

Author:

flixos90

Message:

Editor: Simplify usage of block_has_support() function by supporting a string.

Most block feature checks are for a single feature string, and for such cases it is not intuitive to require an array for the $feature parameter of the block_has_support() function.

This changeset brings it in line with other functions like post_type_supports(), allowing to pass a string for the $feature. An array is still supported for more complex cases where support for sub-features needs to be determined. This change furthermore includes a very minor performance tweak by avoiding calls to the _wp_array_get() function if a single feature string is being checked for.

Props thekt12, nihar007, mukesh27, swissspidy.
Fixes #58532.

File:

• trunk/src/wp-includes/block-supports/settings.php (modified) (2 diffs)

trunk/src/wp-includes/block-supports/settings.php

@@ -41 +41 @@
     // return early if the block doesn't have support for settings.
     $block_type = WP_Block_Type_Registry::get_instance()->get_registered( $block['blockName'] );
-    if ( ! block_has_support( $block_type, array( '__experimentalSettings' ), false ) ) {
+    if ( ! block_has_support( $block_type, '__experimentalSettings', false ) ) {
         return $block_content;
     }
@@ -78 +78 @@
     // Return early if the block has not support for descendent block styles.
     $block_type = WP_Block_Type_Registry::get_instance()->get_registered( $block['blockName'] );
-    if ( ! block_has_support( $block_type, array( '__experimentalSettings' ), false ) ) {
+    if ( ! block_has_support( $block_type, '__experimentalSettings', false ) ) {
         return null;
     }