JS error:

TypeError: "middleware.fields is undefined"

Blocks which uses middleware are not working when the built-in Gutenberg is used with WP 5.0.1.

Maybe because the middleware js is loaded after the editor js. Just a guess.

When installing the gutenberg plugin everything works as expected.

Let me know if this issue needs to be raised in the core Gutenberg plugin instead. . .but the Image field doesn't look right in the Inspector.

Hi

Nice stuff, was looking for a package like this.
I'd like to propose a field type which is extremely useful from my experience - post selection

Thanks

As a Gutenberg Fields Middleware user, it would give me more confidence in using this library if there was some basic test coverage around the generated fields.

Looks interesting. Certainly what I was expecting from Gutenberg in the first place. But...Is this project still active?

https://github.com/WordPress/gutenberg/blob/master/packages/components/src/autocomplete/README.md

When using the image field in the inspector, once an image has been added, there's no option to remove it.

'attributes'      => [
		'backgroundImage' => [
			'type'  => 'object',
			'field' => [
				'type'             => 'image',
				'label'            => __( 'Background Image', 'oshpd' ),
				'placement'        => 'inspector',
				'removeButtonText' => 'Remove',
			],
		],
],

Hey, I've got things working well for Client Side registration, but I'm not able to see blocks registered server side.

Using your example:

register_block_type( 'example-namespace/example-block', array(
        'title' => 'Example Block',
	'attributes' => array(
		'image' => array(
			'type' => 'object',
			'field' => array(
				'type' => 'image',
				'buttonText' => 'Upload',
				'imagePlaceholder' => true,
				'removeButtonText' => 'Remove',
			),
		),
		'color' => array(
			'type' => 'string',
			'field' => array(
				'type' => 'color'
			)
		)
	),
	'render_callback' => 'example_callback',
) );

I don't have an example block in my list of blocks.

I know Gutenberg support for Server Side registry is pretty weak. . .not sure if this is still a limitation of Gutenberg, an issue with this plugin, or just something I'm doing wrong?

Uploading media in media-upload field throws the following error and needs to updated according to the latest changes in Gutenberg.

I've tried this with Gutenberg versions 2.2-2.7 and can't get it to work with any of them.

Steps to Reproduce

• activate Gutenberg v2.2 - 2.7
• activate gutenberg-fields-middleware
• create new post
• try to add "Simple Example Block" to the post
• check your console

This is what I'm seeing, for the most part. . .varies a bit based on the version of Gutenberg:

As a Gutenberg Fields Middleware user, I'd like to be able to many generic fields. It'd be great of the middleware gave me the following:

• Media upload / select from media library
• <select> field.
• <textarea> field.
• TinyMCE editor field.
• Checkboxes / radio buttons
• All HTML5 <input> fields.

Kirki is good for inspiration on which controls could be included:

Hi
I download github project and set active development mode with set IS_GUTENBERG_FIELDS_MIDDLEWARE_DEV to true to active example.
But I have just "Simple Example Block" block and have not advanced settings fields in advanced sidebar:

I have error in console:

gutenberg-fields-middleware.php:

• Version: 0.2

For some reason $attributes in the PHP render_callback function doesn't have the inspector attributes from the JS side.

I also logged prepare_attributes_for_render() and the inspector attributes are not there.

From below, 'image' is in $attributes, 'amount' is not.

Am I missing something? Is it a bug?

Code excerpt:

attributes: {
	image: {
		type: 'object',
		field: {
			type: 'image',
		},
	},
	amount: {
		type: 'number',
		field: {
			type: 'range',
			label: 'Amount',
			placement: 'inspector', // To show in sidebar.
			min: 1,
			max: 10
		},
		default: 2,
	},
},
edit: function( props, middleware ) {
	return [
		middleware.blockControls,
		middleware.inspectorControls,
		middleware.fields.image,
	];

},
save: function( props ) {
	// Rendering in PHP
	return null;
},

I had a brief chat with @danielbachhuber and he suggested I open an issue.

It's more a feedback than a call for action. Core provides a few hooks which allow to modify the block which is about to be registered. See: https://wordpress.org/gutenberg/handbook/extensibility/#modifying-blocks-experimental. In particular blocks.registerBlockType might be another way to go. It probably would have to be set with the top priority to make sure it is executed first.

This is an interesting idea, the more plugins like that, the more ideas for the core part to incorporate it by default. Once it is ready, we should see if it is something that would bring expected benefits to a wider audience. In fact, we use a similar approach in core in a few cases. Examples: https://github.com/WordPress/gutenberg/blob/master/blocks/hooks/align.js, which adds align support for the block with supports: align property.

Currently there is no option to set default value for radio field, if its possible we can add support in Middleware to add default selected value.

For eg.

radio: {
	type: 'string',
	field: {
		type: 'radio',
		label: __( 'Type' ),
		placement: 'inspector',
		default: 'major',
		options: [
			{
				value: 'major',
				label: __( 'Major' ),
			},
			{
				value: 'minor',
				label: __( 'Minor' ),
			},
		],
	},
},

https://github.com/rtCamp/gutenberg-fields-middleware/blob/develop/middleware/fields/button-editable/index.js#L21

Will return

[
    backgroundColor: undefined
    class: undefined
    color: undefined
    link: undefined
]

A big push for Gutenberg right now is to ensure the entire user experience is WCAG-compliant.

We should make sure our generated fields meet accessibility standards.

When we take this issue on, we should also develop some automated way for enforcing field compliance and share those learnings upstream on WordPress/gutenberg#6098

Once #2 is complete, we should document these available fields in the README.md.

Howdy!

What license is this code released under? I see a reference to GPLv2 in the package.json file, but none of the usual text is present.

Thanks!

1. Not able to set dynamic background color and text color using editable button. I also checked with this example . This only works with button but not button-editable.
2. If user navigate using tab, then not able to add text or link.

While creating custom block from Gutenberg we can use valid input types using TextControl.

In Middleware we have support for url, text, range, date-time etc. But missing some other valid input types. For eg. date, time, week, month etc.