REST API: Fixed schema for the Page post type is incorrect

[johnbillion]

The fixed schema for the page post type incorrectly states that it supports the excerpt field. It does not.

Ref: ​https://github.com/WordPress/wordpress-develop/blob/d570de32ca3a5f623bf26d70dfc55141c339073d/src/wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php#L1801-L1831

In addition, I'm not sure why the schemas for the Post, Page, and Attachment post types are hard-coded instead of relying on post type support.

[johnbillion]

Hmm, the attachment post type also states that it supports custom-fields, which it does not.

[danielbachhuber]

I'm not sure why the schemas for the Post, Page, and Attachment post types are hard-coded instead of relying on post type support.

The idea here was that core post types would always have a fixed schema:

• ​https://github.com/WP-API/WP-API/commit/a84f48adead9fa40d5cde949034da5b7a2635403
• ​https://github.com/WP-API/WP-API/pull/844#issuecomment-74586279

I suspect the original conversation is in Slack somewhere...

[johnbillion]

Removing the excerpt field from the response when querying Pages could be considered a breaking change. What's the best path forward?

[joehoyle]

Woops, I guess we made them all adhere to an incorrect schema at the beginning. I don't know if there's much we can do about this now. Maybe make them read-only?

[TimothyBlynJacobs]

I agree, I'm not sure there is much we can do here at this point without breaking BC. Particularly three years later. If someone wants to own it, feel free to reopen.