Expose Gutenberg Data Format version in the REST API

[pento]

Description

As described in #6435, it would be valuable to third party tools if we exposed a canonical block format version for the content of the current post, so they could decide how to handle the post.

For now, this is simply 0, for "no blocks", or 1, for "yes, there are blocks".

Checklist:

• My code is tested.
• My code follows the WordPress code style.
• My code follows the accessibility standards.
• My code has proper inline documentation.

[ocean90]

Typo: uses

[gziolo]

551 | ERROR | [x] File must end with a newline character
| | (Generic.Files.EndFileNewline.NotFound)

From our friend phpcs.

[pento]

🕺🏻

[danielbachhuber]

I don't love this solution to the problem, as it seems to fall into the category of "let's shove a bunch of extra data onto the Post resource."

Can you describe the other approaches proposed?

We have a protected subattribute of content. Is block_version better suited on content, given Gutenberg works directly with the post content?

[pento]

@danielbachhuber: I agree, that's definitely a better place to put it. Is there a filter for the schema that would let me add that? If not, register_rest_field() with a copy/pasta of the full content property from WP_REST_Posts_Controller is a reasonable hack for now.

[pento]

Actually, I just went with adding it to the post response for now. We can do it properly in the merge.

[mcsf]

Works and looks alright to me. I might wait for a second opinion, up to you. :)

[danielbachhuber]

I've added a @todo marker for registering on the schema.