WordPress/wp-includes/rest-api
TimothyBlynJacobs 41f70ae5f8 REST API: Only register one block renderer route.
Every block has a different set of attributes. These attributes are specified as a JSON Schema object. Previously, every block registered its own block renderer route using its attributes for the schema. This allowed for the attributes to be validated using the built in endpoint validation rules. It had the unfortunate side effect, however, of creating a large number of nearly identical REST API routes, one for each dynamic block. Each registered route has a performance impact. As the number of server side blocks goes up, this becomes more and more of an issue.

Now, we register a single block renderer route and dynamically validate the attributes based on the selected block.

Fixes #48079.
Props gziolo, TimothyBlynJacobs.

Built from https://develop.svn.wordpress.org/trunk@48069


git-svn-id: http://core.svn.wordpress.org/trunk@47836 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2020-06-17 03:22:12 +00:00
..
endpoints REST API: Only register one block renderer route. 2020-06-17 03:22:12 +00:00
fields REST API: Fix updating "multiple" meta keys with non-string values. 2020-06-10 02:22:13 +00:00
search Docs: Add missing `@see` tag to `WP_REST_Post_Search_Handler` DocBlock. 2019-05-14 15:00:07 +00:00
class-wp-rest-request.php REST API: Handle parameter types consistently within set_param(). 2020-04-09 19:30:07 +00:00
class-wp-rest-response.php Docs: Improve inline comments per the documentation standards. 2020-01-29 00:45:18 +00:00
class-wp-rest-server.php General: Remove or add inline comments to `$HTTP_RAW_POST_DATA` occurrences. 2020-06-08 19:55:10 +00:00