Bernie Reiter

> > I'm assuming we're going to need to open a GB counterpart to deal with the same logic for adding variation class names in the editor too? > >...

To make this easier to test, we might want to consider fixing https://github.com/WordPress/gutenberg/issues/63077 first. This will allow us to switch an existing Core block that currently uses `variation_callback` to setting...

> This is just a bit of a random thought but, is adding a field for each type of PHP file that might be needed the best path forward, instead...

Is there any way we could go with option 1 _without_ requiring access to block context from the block editor store -- instead providing it to whatever action or selector...

Adding another request shared by @getdave in Slack: > Missing entities has been a problem in the Nav block. For 6.9 I had to implement our own `getEntityRecords` calls to...

Hey @caseyjmilne, thank you for your feedback! This is one of the most thorough reviews of Block Bindings I've seen for WP 6.9, and I really appreciate it! Find my...

Unit tests are currently failing due to a built-in check in Core's `src/wp-includes/rest-api.php`. The following patch would be required to make them pass: ```diff diff --git a/src/wp-includes/rest-api.php b/src/wp-includes/rest-api.php index d33a52ef51..841848cf56...

> Why is the current "rich-text" type not breaking these unit tests? That's a good question. I haven't been able to locate any code dedicated to handling that type yet....

## Discussion I'd like to discuss if this could still be considered for WP 6.9. I realize that introducing an addition to `block.json` so late in the cycle could be...

Thanks a lot @gziolo! Really appreciate your feedback ❤️ I'll open this PR for wider review, including by Editor Tech Leads for 6.9 and other interested parties. Y'all -- would...