Add support for `ancestor` block.json property for on-page block plugin search, and insertion

[randhirexpresstech]

If a block plugin use ancestor-child relationship blocks then there are following issue occurs:

1. Search feature for block plugin inside the Block Editor results in child block, instead it should show the ancestor (or main) block name.

2. After block plugin installation on-page via block-editor, Block editor try to insert child block instead of ancestor block. As a result, admin don't get to see any block inside page after block plugin installation.

Block plugin validator recently fixed a bug - Add support for ancestor block.json property https://meta.trac.wordpress.org/ticket/6465 but still there are some issues left for fixed inside block editor.

[ryelle]

@randhirexpresstech I just tried to replicate this on the latest version of Gutenberg, and when I search for form I get the parent Form block (gutena/forms). I can't seem to get the Confirmation block to show up even if I search for confirmation. Are you still seeing this issue?

[randhirexpresstech]

Replying to ryelle:

@randhirexpresstech I just tried to replicate this on the latest version of Gutenberg, and when I search for form I get the parent Form block (gutena/forms). I can't seem to get the Confirmation block to show up even if I search for confirmation. Are you still seeing this issue?

Thanks @ryelle for checking this issue. After getting this issue we reverted back our changes in our block plugin. You can replicate this issue by changing parent to ancestor in child block's block.json in any block plugin which is submitted to wordpress.org block directory.

[apedestrian]

I am also experiencing this with my plugin that includes 3 blocks (​https://wordpress.org/plugins/infinite-scroll-block/).

My top level block (apedestrian/infinite-scroll) uses core/query as the parent while my other 2 use apedestrian/infinite-scroll. Despite this, the "Loading" child block is the only result when searching infinite scroll inside the editor

I am using "parent" instead of "ancestor" inside all the block.json files

[apedestrian]

I removed then added my plugin back to the block repository via the ​validator tool and that fixed my issue