[wp-trac] [WordPress Trac] #62002: Extend Block Metadata PHP Cache to Third-Party Blocks

WordPress Trac noreply at wordpress.org
Mon Sep 30 17:25:02 UTC 2024


#62002: Extend Block Metadata PHP Cache to Third-Party Blocks
-------------------------------------------------+-------------------------
 Reporter:  mreishus                             |       Owner:  flixos90
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:  6.7
Component:  Editor                               |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests commit      |     Focuses:
  needs-dev-note                                 |  performance
-------------------------------------------------+-------------------------

Comment (by flixos90):

 Replying to [comment:27 gziolo]:
 > > Is there already tooling available to generate the kind of block
 metadata manifest file needed for this API? In other words, where does
 this happen for the Core blocks?
 >
 > It isn't part of `@wordpress/scripts`. So far, it has been implemented
 only in WordPress core, but I don't have enough insights on whether it's
 integrated on the webpack or grunt level. That's said, I would be game of
 providing a way to offer a simple and performant way to register multiple
 blocks with one function call that internally combines the new API for
 registering the metadata cache collection and using it to generate all
 individual blocks listed.

 I opened a Gutenberg issue to get this added to `@wordpress/scripts`:
 https://github.com/WordPress/gutenberg/issues/65758

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


More information about the wp-trac mailing list