[wp-meta] [Making WordPress.org] #5303: Block plugin validation tool UI improvements

Making WordPress.org noreply at wordpress.org
Wed Jul 8 06:36:01 UTC 2020

#5303: Block plugin validation tool UI improvements
 Reporter:  tellyworth        |       Owner:  (none)
     Type:  task              |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |

Comment (by tellyworth):

 Replying to [comment:5 ryelle]:
 > [attachment:"single-parent-block.diff"] This check is just an idea, I
 don't think we've officially made it a rule — there should be only one
 "top level" block per block-plugin. Having a single block ID'd as the
 "main block" would be helpful for the block dir API too, make sure we're
 showing the right block name.

 Yep this is great. At the moment there's a much lazier check which blindly
 assumes that < 5 blocks might be parent/child blocks but 5+ is too many.
 It definitely should be a rule that there's only one top level block. I
 did have an earlier idea that we could enforce only one `block.json` file
 per plugin, with that file representing the top-level block. But this is
 much more comprehensive. It seems reasonable to say "if you want to
 include multiple parent/child blocks, you need to use `block.json` files
 for all of them with the correct `parent` values."

 Let's put this in, and update the 5 block rule in `check_for_blocks` to be
 a higher number. At some point if there are, I dunno, 15 or 20 blocks in
 there, even if the parent/child relationship is configured correctly it
 might be a sign that something's gone wrong.

Ticket URL: <https://meta.trac.wordpress.org/ticket/5303#comment:7>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list