Greg Ziółkowski
Greg Ziółkowski
> I tend to agree with @kkmuffme, but I do think this would be a breaking change for `@wordpress/scripts`, so I didn't want to merge that without more feedback :)...
I landed on this proposal thanks to the [WP Tavern article](https://wptavern.com/featured-cover-blocks-and-the-future-of-binding-data-to-generic-wordpress-blocks) by @justintadlock. I wanted to share that @dmsnell is actively exploring how we could formalize the concept of dynamic...
The improved Pattern block, as described in https://github.com/WordPress/gutenberg/issues/48458, might also need integration with a similar system as covered in this issue. It gets even more interesting when you pair Pattern...
@mtias and @SantosGuillamot, how much the new [Custom fields 🔗 Blocks](https://github.com/WordPress/gutenberg/issues/51373) project relates to this issue? It seems the goals for block attributes align. There is also [Tracking issue: Connecting...
The initial rollout in the WordPress 6.5 release introduces a way to define the bindings with block attributes and supporting API on the server that allows registering sources on the...
@jakeparis, thank you for opening this proposal. Actually, it's something that has been on the Block API roadmap https://github.com/WordPress/gutenberg/issues/41236 for quite some time, but it didn't have a related issue....
> Big fan of this PR, ACF Blocks users often are confused by the requirement for an `.asset.php` file to exist, especially as the documentation says "you may" but it...
The other idea I shared in https://github.com/WordPress/gutenberg/issues/57234#issuecomment-1866091936, that instead of tweaking the format of `block.json`, we could put a filter that allows modifying all the params that get passed to...
> The thing I like about this PR is that it would allow you to build a simple block, regardless of type, without having to create one additional file (and...
Do we have a WordPress Trac ticket we could reference in the PR? I think it will become an official recommendation soon for PHP changes that we know require backporting...