[wp-meta] [Making WordPress.org] #6465: Add support for `ancestor` block.json property
Making WordPress.org
noreply at wordpress.org
Wed Jan 4 04:17:50 UTC 2023
#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 |
------------------------------+-------------------------
Changes (by tellyworth):
* owner: (none) => tellyworth
* status: new => accepted
Comment:
The patch attachment:6465.diff seems to do the trick. It essentially
treats parent and ancestor as the same. It's a bit stricter than the old
check though, requiring that the parent/ancestor block exists within the
same plugin. That's so that a block with a parent like `core/column` is
correctly treated as top-level for validation purposes.
It works ok for me at a quick test; do I have the logic right?
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/6465#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list