You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently most core blocks are defined in gutenberg/blocks/build/index.js and gutenberg/editor/build/index.js (PS I'm using the plugin from dotorg)
I want to set up some conditionals depending on what blocks are in a post. And I want a user to select which blocks are allowed. But for that I need to fill a select with the blocks.
It's doable to fill the select with JS if you wp_enqueue_script( 'wp-blocks' ); on the pages you need, but then you are loading most of gutenburg on that page just to get the blocks.
I've red the way to add new blocks
Shouldn't there be an other way to do this?
Putting this in the rest API seems like a nice way to do this.
The text was updated successfully, but these errors were encountered:
Yes, it's been proposed that all blocks should have some amount of a server definition. Considering this as a duplicate of #2751, but the reference will prove valuable as a concrete use-case. Thanks!
Currently most core blocks are defined in
gutenberg/blocks/build/index.js
andgutenberg/editor/build/index.js
(PS I'm using the plugin from dotorg)I want to set up some conditionals depending on what blocks are in a post. And I want a user to select which blocks are allowed. But for that I need to fill a select with the blocks.
It's doable to fill the select with JS if you
wp_enqueue_script( 'wp-blocks' );
on the pages you need, but then you are loading most of gutenburg on that page just to get the blocks.I've red the way to add new blocks
Shouldn't there be an other way to do this?
Putting this in the rest API seems like a nice way to do this.
The text was updated successfully, but these errors were encountered: