Make WordPress Core


Ignore:
Timestamp:
08/10/2023 04:47:00 PM (10 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:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/src/wp-includes/block-supports/custom-classname.php

    r54873 r56382  
    1616 */
    1717function wp_register_custom_classname_support( $block_type ) {
    18     $has_custom_classname_support = block_has_support( $block_type, array( 'customClassName' ), true );
     18    $has_custom_classname_support = block_has_support( $block_type, 'customClassName', true );
    1919
    2020    if ( $has_custom_classname_support ) {
     
    4343 */
    4444function wp_apply_custom_classname_support( $block_type, $block_attributes ) {
    45     $has_custom_classname_support = block_has_support( $block_type, array( 'customClassName' ), true );
     45    $has_custom_classname_support = block_has_support( $block_type, 'customClassName', true );
    4646    $attributes                   = array();
    4747    if ( $has_custom_classname_support ) {
Note: See TracChangeset for help on using the changeset viewer.