[wp-meta] [Making WordPress.org] #6465: Add support for `ancestor` block.json property

[Making WordPress.org]

#6465: Add support for `ancestor` block.json property
------------------------------+-------------------------
 Reporter:  dd32              |       Owner:  tellyworth
     Type:  defect (bug)      |      Status:  accepted
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  needs-patch       |
------------------------------+-------------------------

Comment (by dd32):

 > It works ok for me at a quick test; do I have the logic right?

 I think the logic is right. For the list below, `parent` means `ancestor
 or parent`.

 - If the block has no parent it's top-level
 - If the block has a parent that's ''not'' provided by the plugin, it's
 top-level.
 - If the block has a parent that's provided by the plugin, it's child.

 A plugin with a block that requires a parent element that's provided by
 another plugin will be treated as a top-level block here (ie. A plugin
 provides "File Upload Block" for "Form Builder Plugin") that'll be treated
 as top-level here, which seems somewhat appropriate.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/6465#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org