[wp-trac] [WordPress Trac] #62140: Consider allowing themes to register block metadata collections

[WordPress Trac]

#62140: Consider allowing themes to register block metadata collections
--------------------------+---------------------
 Reporter:  flixos90      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  6.7.1
Component:  Editor        |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:
--------------------------+---------------------

Comment (by dougwollison):

 Replying to [comment:12 flixos90]:
 > To use the new block metadata collection API, you need to create a
 manifest, which you can reasonably do for your plugin, maybe even a few
 plugins manually, but you realistically can't create a manifest that works
 for all blocks from all plugins. Additionally, if it was possible to
 register a collection for `wp-content/plugins`, different plugins might
 just try to override each other.

 Oh, I wasn't advocating for such an insane use case. I was interpreting
 this limitation as a security measure (that doesn't secure much), not
 code-enforced rule of best practice.

 If we only open up collection registration /themes/* and /mu-plugins/*,
 I'm good. I'm only citing other edge cases like symlinked directories.
 Perhaps a disallow approach would be better, if anything.

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