jan-clockworkwp

@mrclay nice one! Thanks for an update. One additional question, to learn something new everyday, if you don't mind. How do you run your `.ts` script file? Are you using...

@mrclay thanks a lot for confirming that. I really appreciated you script, saved me a lot of time. If I could suggest one small improvement to your script to make...

Hi @theodesp my experience is that since WordPress core 6.5, I had to apply this dirty tweak https://github.com/wpengine/faustjs/issues/1706#issuecomment-2047335782 to be able to see custom blocks generated via `faust blockset` script...

Hey @theodesp, thanks for the heads up on the reason why. It makes sense. My question is, what can we do about it? The problem of not seeing the custom...

@theodesp Perfect, sounds great. I have tried the updated package version 1.3.2 on WP Core v6.5.5, and indeed, custom blocks are now working in WP admin even if the `index.asset.php`...

I would just like to add, that when this check is performed on the client, issue is not present. But cannot guarantee as currently I am getting these errors for...

I can replicate the issue as well with the vanilla faust example setup.

Well done @theodesp, both radio and checkbox controls are working now. I have just one comment that probably an update in the [Faust official docs](https://faustjs.org/tutorial/react-components-to-gutenberg-blocks) is needed. Let me explain...

Hi @josephfusco, thanks for your suggestion. I did a similar Faust core block override on my end; I just thought that it should be a part of the Faustjs package,...

I can confirm that this is still happening as of - "wpengine/wp-graphql-content-blocks": "4.3.2" - "wpackagist-plugin/wp-graphql": "1.29.3" and - "@faustwp/block-editor-utils": "0.3.0", - "@faustwp/blocks": "^5.0.0", - "@faustwp/cli": "3.1.1", - "@faustwp/core": "3.1.0", if...