If you define a text_list with the option 'clone' => true the graphql model should be an array of string arrays otherwise you will get an graphql error when quering the custom fields.

function ingredients_register_meta_boxes( $meta_boxes ) {
	$meta_boxes[] = [
		'title'      => esc_html__( 'Ingredients' ),
		'id'         => 'zutaten',
		'post_types' => ['ingredients'],
		'context'    => 'normal',
		'priority'   => 'high',
		'fields'     => [
			[
				'type'    => 'text_list',
				'id'      => 'ingredients',
				'name'    => esc_html__( 'Ingredients' ),
				'desc'    => esc_html__( 'Specify the ingredients' ),
				'clone'   => true,
				'options' => [
					'100'    => 'Amount',
                                        'ml'     => 'Unit',
                                        'Water' => 'Name',
				],
				'graphql_name' => 'ingredients',
			],
		],
	];

	return $meta_boxes;
}

add_filter( 'rwmb_meta_boxes', 'ingredients_register_meta_boxes' );

I also provided a fix with this PR: #28

This needs some investigation. Complex type fields (ie post, user) could be handled in different ways;

• single field (eg Instructor (user) for a Tutorial (post) can be resolved by looking up the type and getting the graphql_single_name. No edge data.
• multiple fields (eg Questions (post) on a Quiz (post) can be resolved by registering a graphql connection between the two types. Edge data.

Users can be resolved by using the context:

'patient' => [
	'type'        => 'User',
	'resolve'        => function ($payload, $args, $context, $info){
		$userId = $payload['user_id'];
		return $context->get_loader( 'user' )->load_deferred( $userId )
	},
],

Hi,

I just added the email type fields. They are probably not in the Meta Box documentation because they behave exactly the same as the text fields with the difference that the input validation is added.

Now that my PR has been merged into MB we can look into working on mutations.

From memory it used to be difficult to hook into WPGraphQL generated mutations. Previously I registered a new mutation to deal with custom fields.

What this needs:

• mutation input args; the mutation needs to be aware there are new fields as input
• hook into this action to run rwmb_set_meta

This plugin will be much larger than previous WordPress plugins I have written. I will need to have a few helper/resolver classes.

• User resolver
• Post resolver
• Settings resolver
• Meta Box type utility function

Give generating mutations inputs a go.

Some things to note:

• taxonomy fields are already added as inputs to mutations -> no work necessary
• this uses rwmb_set_meta function to set the meta data -> this should work with both custom tables and wp_meta fields
• untested with users, posts etc
• add graphql_mutate to your field config to generate

If you define a text_list with the option 'clone' => true the graphql model should be an array of string arrays.

function ingredients_register_meta_boxes( $meta_boxes ) {
	$meta_boxes[] = [
		'title'      => esc_html__( 'Ingredients' ),
		'id'         => 'zutaten',
		'post_types' => ['ingredients'],
		'context'    => 'normal',
		'priority'   => 'high',
		'fields'     => [
			[
				'type'    => 'text_list',
				'id'      => 'ingredients',
				'name'    => esc_html__( 'Ingredients' ),
				'desc'    => esc_html__( 'Specify the ingredients' ),
				'clone'   => true,
				'options' => [
					'100'    => 'Amount',
                                        'ml'     => 'Unit',
                                        'Water' => 'Name',
				],
				'graphql_name' => 'ingredients',
			],
		],
	];

	return $meta_boxes;
}

add_filter( 'rwmb_meta_boxes', 'ingredients_register_meta_boxes' );

• resolve linked post types from fields
• update some other types to respect the multiple === true setting
• fixed bad dependency check on MB Relationship not MB core

Check out fields that can be multiple (eg users) and handle their graphql types:

If type is text and multiple = false should be String If type is text and multiple = true should be ['list_of' => 'String']

It seems that v1.6 introduced Lazy Type Loading https://github.com/wp-graphql/wp-graphql/issues/2049

So, I'm getting the following error while using your extension

ERROR

gatsby-source-wordpress Error category: undefined

Error: Internal server error

Debug message: Return value of GraphQL\Type\Schema::resolveType() must be an instance of GraphQL\Type\Definition\Type, array returned

Error path: __schema.types

ERROR #gatsby-source-wordpress_111002

Any chance for an update or a clue of what needs to be updated?

I'm not adept enough with WP to ensure I have correctly hooked into the request lifecycle. The code works, but is it efficient? Not sure. Hopefully someone can provide some insight and refactor the loading code.

I've seen nice autoloading code in Meta Box plugins, but I never bothered to implement it in this plugin. Maybe someone could submit a PR cleaning up the loading of source files.

I have not written tests as I'm not skilled with writing tests for WordPress/PHP. This should have some level of sanity testing to ensure no regressions from version to version.

If I could get some test scaffolding done I can fill in the necessary tests from the GraphQL standpoint.

Have you looked into supporting metabox settings pages at all? I'm just getting started with wp-graphql, and I see that settings registered via register_settings() are natively supported, but I'm not quite sure where to get started if I would want some of my metabox.io created settings pages registered for graphql?