SSR blocks with enum attribute thows notice

[walbo]

Server side rendering a block that has a enum attribute without a type throws an notice that says type in undefined in the rest api.

The rest api should require either a type or an enum.

Ex on block that will fail:

<?php
register_block_type(
    'core/example',
    array(
        'attributes'      => array(
            'value'    => array(
                'enum' => [ 'ok', false ],
            ),
        ),
        'render_callback' => function( $block_attributes ) {
            return $block_attributes['value'];
        },
    )
);

Trac ticket: https://core.trac.wordpress.org/ticket/54386

[walbo]

Added a quick unit test to show the failure.

[TimothyBlynJacobs]

Can you clarify what you would like to see changed here? The REST API requires a type argument. If you want to use an enum that crosses types, you should specify each of the types as a list.

[walbo]

Yes, that will solve it.

The ​block attributes documentation clearly states either a type or an enum is required:

The attribute definition will contain, at a minimum, either a type or an enum. There may be additional fields.

So the question is: Should the REST API support having enum without a required type?

If not I quess this ticket can be closed and I'll create an issue in the Gutenberg repo to update the docs and examples.

[TimothyBlynJacobs]

Yeah, this should be reported upstream as a docs issue. The WordPress REST API supports loose typing which mostly necessitates us to have types defined even where the core JSON Schema spec wouldn't require them.