Enqueue block assets with 'enqueue_block_assets' action

[ouun]

Refactor assets() call to support (a) cached blocks & (b) the iframed Block Editor & Site Editor.

For more detailse see #304.

[ouun]

@Log1x it would be great to get your feedback on this. Do you think we could get it in a patch release? THX

[Log1x]

hey, sorry for the delay. this looks good. i think we could have the upgrade script update the assets with $block to without?

[Log1x]

i do see ACF Pro still using enqueue_block_editor_assets internally. im a little behind on this iframe vs non-iframed stuff – when are you required to use one over the other?

[ouun]

i do see ACF Pro still using enqueue_block_editor_assets internally. im a little behind on this iframe vs non-iframed stuff – when are you required to use one over the other?

• enqueue_block_editor_assets for the assets that target the editor, e.g. for adding editor specific plugins/functionality/hooks.
• enqueue_block_assets for the content within the editor (iframe & non-iframe + frontend & backend).

You can see the difference for WP >6.3 here: WordPress/gutenberg#53236 (comment)

Thanks a lot as always for your support!

[ouun]

As discussed we stick with enqueue_block_assets and pass $block to assets().