[wp-trac] [WordPress Trac] #48079: REST API: optimize how the schema API is generated for block-renderer endpoints

[WordPress Trac]

#48079: REST API: optimize how the schema API is generated for block-renderer
endpoints
-------------------------+------------------------------
 Reporter:  gziolo       |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  REST API     |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:
-------------------------+------------------------------

Comment (by gziolo):

 This is a more broad issue as presented on screenshots shared. It's not
 only about the overhead that REST API schema creates. It's also about the
 size of HTML output we produce to be served when the edit post page loads.
 There are two factors involved:
 - all REST API endpoints created for every block registered on the server
 - block definitions exposed for every block registered on the server

 I personally could argue whether Social Link block should have 37
 instances registered on the server. However, I'm aware that in WordPress
 5.4 we all hope to see all core blocks to be registered on the server.
 Moreover, in the future, we want to have a proper REST API endpoint which
 returns all definitions for blocks registered on the server as described
 in [47620].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/48079#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform