I get an error on a fresh install of this package in my plugin. I never used to, the only thing I've done is upgraded WP GraphQL to 1.2.5. In GraphiQL, I get:

{
  "code": "internal_server_error",
  "message": "<p>There has been a critical error on this website.</p><p><a href=\"https://wordpress.org/support/article/debugging-in-wordpress/\">Learn more about debugging in WordPress.</a></p>",
  "data": {
    "status": 500
  },
  "additional_errors": []
}

Inspecting the debug log, I see:

[08-Mar-2021 15:00:46 UTC] PHP Notice:  Undefined property: WP_Post_Type::$graphql_single_name in /var/www/html/wpgraphql_crb_test/wp-content/plugins/graphql-carbon-test/vendor/matepaiva/wp-graphql-crb/src/Container.php on line 203
[08-Mar-2021 15:00:46 UTC] PHP Notice:  Undefined property: WP_Post_Type::$graphql_single_name in /var/www/html/wpgraphql_crb_test/wp-content/plugins/graphql-carbon-test/vendor/matepaiva/wp-graphql-crb/src/Container.php on line 203
[08-Mar-2021 15:00:46 UTC] PHP Notice:  Undefined property: WP_Post_Type::$graphql_single_name in /var/www/html/wpgraphql_crb_test/wp-content/plugins/graphql-carbon-test/vendor/matepaiva/wp-graphql-crb/src/Container.php on line 203
[08-Mar-2021 15:00:46 UTC] PHP Notice:  Undefined property: WP_Post_Type::$graphql_single_name in /var/www/html/wpgraphql_crb_test/wp-content/plugins/graphql-carbon-test/vendor/matepaiva/wp-graphql-crb/src/Container.php on line 203
[08-Mar-2021 15:00:46 UTC] PHP Notice:  Undefined property: WP_Post_Type::$graphql_single_name in /var/www/html/wpgraphql_crb_test/wp-content/plugins/graphql-carbon-test/vendor/matepaiva/wp-graphql-crb/src/Container.php on line 203
[08-Mar-2021 15:00:46 UTC] PHP Notice:  Undefined property: WP_Post_Type::$graphql_single_name in /var/www/html/wpgraphql_crb_test/wp-content/plugins/graphql-carbon-test/vendor/matepaiva/wp-graphql-crb/src/Container.php on line 203
[08-Mar-2021 15:00:46 UTC] PHP Notice:  Undefined property: WP_Post_Type::$graphql_single_name in /var/www/html/wpgraphql_crb_test/wp-content/plugins/graphql-carbon-test/vendor/matepaiva/wp-graphql-crb/src/Container.php on line 203
[08-Mar-2021 15:00:46 UTC] PHP Fatal error:  Uncaught TypeError: Argument 1 passed to register_graphql_field() must be of the type string, null given, called in /var/www/html/wpgraphql_crb_test/wp-content/plugins/graphql-carbon-test/vendor/matepaiva/wp-graphql-crb/src/Container.php on line 47 and defined in /var/www/html/wpgraphql_crb_test/wp-content/plugins/wp-graphql/access-functions.php:269
Stack trace:
#0 /var/www/html/wpgraphql_crb_test/wp-content/plugins/graphql-carbon-test/vendor/matepaiva/wp-graphql-crb/src/Container.php(47): register_graphql_field()
#1 /var/www/html/wpgraphql_crb_test/wp-content/plugins/graphql-carbon-test/vendor/matepaiva/wp-graphql-crb/src/Container.php(63): WpGraphQLCrb\Container->registerField()
#2 /var/www/html/wpgraphql_crb_test/wp-content/plugins/graphql-carbon-test/vendor/matepaiva/wp-graphql-crb/src/Container.php(57): WpGraphQLCrb\Container->registerFields()
#3 /var/www/html/wpgraphql_crb_test/wp-includes/class-wp-hook.php(287): WpGraphQLCrb\Container->graphqlRegisterTypes()
#4 /var/www/html/wpgraphql_crb_test/wp-inclu in /var/www/html/wpgraphql_crb_test/wp-content/plugins/wp-graphql/access-functions.php on line 269

And digging deeper, I find that for the WpGraphQLCrb\Container instance, the getGraphQLRoot() method is returning:

Array
(
    [0] => post
    [1] => page
    [2] => mediaItem
    [3] => 
    [4] => 
    [5] => 
    [6] => 
    [7] => 
    [8] => 
    [9] => 
)

This array is mapped from Carbon_Fields\REST_API\Decorator::get_post_meta_container_settings() using the map function $type -> getGraphQLPostTypeRoot($type). The array provided from that mapping is:

Array
(
    [0] => post
    [1] => page
    [2] => attachment
    [3] => revision
    [4] => nav_menu_item
    [5] => custom_css
    [6] => customize_changeset
    [7] => oembed_cache
    [8] => user_request
    [9] => wp_block
)

So it seems that Container->getGraphQLPostTypeRoot($type) is failing for revision, nav_menu_item, custom_css... etc, as those post type objects don't have a graphql_single_name.

My composer json:

{
    "require": {
        "htmlburger/carbon-fields": "^3.2",
        "matepaiva/wp-graphql-crb": "dev-master"
    },
    "minimum-stability": "dev",
    "prefer-stable": true
}

Installed plugins: WP GraphQL (Version 1.2.5)

My code:

<?php
/*
Plugin Name: WPGraphQL Carbon Fields Test
Version: 1.0
*/

namespace GraphQLCarbonTest;

use WpGraphQLCrb\Container as WpGraphQLCrbContainer;
use Carbon_Fields\Container;
use Carbon_Fields\Field;

add_action( 'carbon_fields_register_fields', 'GraphQLCarbonTest\crb_attach_theme_options' );
function crb_attach_theme_options() {
	WpGraphQLCrbContainer::register(
    Container::make( 'post_meta', __( 'Test Post Meta Container' ) )
        ->add_fields( array(
            Field::make( 'text', 'crb_text', 'Text Field' ),
            // Field::make( 'icon', 'sm_download_icon', __( 'Icon', 'crb' ) ),
        ) )
	);
}

add_action( 'after_setup_theme', 'GraphQLCarbonTest\crb_load' );
function crb_load() {
    require_once( 'vendor/autoload.php' );
    \Carbon_Fields\Carbon_Fields::boot();
}

I'm thinking that removing these types from the $roots whose post type objects don't have a graphql_single_name would solve the issue, but I'm not confident that it wouldn't break anything else. What do you think?

I've a association field with a custom subtype and multiple types, like this:

Field::make('association', 'test', __('Materials:'))
    ->set_types(
        array(
            array(
                'type'      => 'post',
                'post_type' => 'materials',
            ),
            array(
                'type'      => 'term',
                'taxonomy' => 'material_category'
            )
        )
    )

If the graphql_single_name option (from the post type or taxonomy) not starts with an uppercase letter, it results in a graphql error: Type loader is expected to return type "materialCategory", but it returned "MaterialCategory".

I took a look at it and saw that register_graphql_union_type function, triggers a prepare_type function that uses ucfirst for the type name. The following fix works for me.

diff --git a/src/Field.php b/src/Field.php
index 0ea53e9..b1a9bf6 100644
--- a/src/Field.php
+++ b/src/Field.php
@@ -193,7 +193,7 @@ private function getTypeFromAssociation()
             return 'Post';
           }
 
-          return $graphql_single_name;
+          return ucfirst($graphql_single_name);
         }
 
         if ($object instanceof Term) {
@@ -206,7 +206,7 @@ private function getTypeFromAssociation()
             return 'Tag';
           }
 
-          return $taxonomy_name;
+          return ucfirst($taxonomy_name);
         }
 
         if ($object instanceof Comment) {

Hi,

If I try to run GraphQL Code Generator, I get the following error: Type Crb_ThemeOptions must define one or more fields.

I think one possible solution would be:

diff --git a/src/Container.php b/src/Container.php
index aaee152..284437e 100644
--- a/src/Container.php
+++ b/src/Container.php
@@ -21,6 +21,8 @@ class Container
 {
   private static $is_first_time = true;
 
+  private static $is_first_time_theme_options = true;
+
   public function __construct(CrbContainer $container)
   {
     $this->container = $container;
@@ -54,6 +56,12 @@ public function graphqlRegisterTypes()
       Container::$is_first_time = false;
       Container::registerStaticObjectTypes();
     }
+
+    if ($this->container->type === 'theme_options' && Container::$is_first_time_theme_options) {
+      Container::$is_first_time_theme_options = false;
+      Container::registerStaticThemeOptionObjectTypes();
+    }
+
     $this->registerFields();
   }
 
@@ -64,12 +72,14 @@ private function registerFields()
     }
   }
 
-  static function registerStaticObjectTypes()
+  static function registerStaticThemeOptionObjectTypes()
   {
-    register_graphql_object_type('Crb_ThemeOptions', [
-      'description' => \__("All the Carbon Field Theme Options", 'app'),
-      'fields' => [],
-    ]);
+    register_graphql_object_type(
+        'Crb_ThemeOptions', [
+        'description' => \__("All the Carbon Field Theme Options", 'app'),
+        'fields' => [],
+      ]
+    );
 
     register_graphql_field(
       'RootQuery',
@@ -81,7 +91,10 @@ static function registerStaticObjectTypes()
         }
       ]
     );
+  }
 
+  static function registerStaticObjectTypes()
+  {
     register_graphql_object_type('Crb_Select', [
       'description' => \__("The selected option/radio", 'app'),
       'fields' => [

Or do you've another idea?

Hello! I've decided to use your plugin along with Carbon fields (v. 3.2) and WPGraphQL. Unfortunately the theme_options field doesn't show up in the GraphQL IDE in my wordpress (v. 5.6). My theme options container looks like this:

WpGraphQLCrbContainer::register(
    Container::make( 'theme_options', __( 'Theme Options' ) )
        ->add_tab( 'Footer', [
            Field::make( 'text', 'footer_text', 'Footer text' ),
        ] )
);

Adding ->set_visible_in_rest_api(true) didn't change anything. Is this something expected, maybe you can help me with this problem?

Kind regards, Jakub.

I tried getting a complex field from a theme option, but I get an error in Container.php line 176 that the callback expected 6 arguments but was passed 3.

Only the getScalar resolver seems to accept only three arguments, so I guess this is a bug?

Following the 'Usage' in the readme, and installing the package using the following:

composer require matepaiva/wp-graphql-crb

...I am faced with the following:

Could not find a version of package matepaiva/wp-graphql-crb matching your minimum-stability (stable). Require it with an explicit version constraint allowing its desired stability.

What is the recommended way to install?

Before this commit, a carbon field type rich_text when queried via graphql would return a string like:

first paragraph
\r\n\r\n
second paragraph

From now on, it will return a HTML parsed string:

<p>first paragraph</p>
\n
<p>second paragraph</p>

Hey, I'm trying to work with Map carbon field, but when use wpgraphql to retrieve the value it returns an error, because it expects string, but the returned value from map field is array with 5 items (value, lat, lng, zoom, address).

Field::make('map', 'location', __('Location', 'crb'));

I could use graphql_resolve_field filter to return $result['value'] as a string. In my case (where the field name is 'location') I can not choose nested nodes (value, lat, lng, zoom or address), I have just "location".

I was thinking in a good semantic way of matching Conditional Fields with GraphQL. Something like that:

{
  institutionalContents {
    nodes {
      title
      excerpt
      action { # this name comes from set_conditional_logic.field 
        ... on NewsletterSubscribeAction { # this name comes from set_conditional_logic.value + set_conditional_logic.field
          textFieldPlaceholder
          textFieldLabel
          buttonText
        }
        ... on LinkAction {
          href
          label
        }
      }
    }
  }
}

The idea is using Inline Fragments, grouping fields with the same set_conditional_logic within the same Carbon Container. I don't know if it is a good idea so I want to know your opinion. In the case above, the carbon fields would be something like that:

      Field::make('select', 'action', 'Ação')->set_options([
        'link' => 'Link',
        'newsletter_subscribe' => 'Newsletter Subscribe',
      ]),
      
      // Link
      Field::make('text', 'href', 'href')->set_conditional_logic([['field' => 'action', 'value' => 'link']]),
      Field::make('text', 'label', 'label')->set_conditional_logic([['field' => 'action', 'value' => 'link']]),

      // Newsletter Subscribe
      Field::make('text', 'text_field_label', 'text_field_label')->set_conditional_logic([['field' => 'action', 'value' => 'newsletter_subscribe']]),
      Field::make('text', 'text_field_placeholder', 'text_field_placeholder')->set_conditional_logic([['field' => 'action', 'value' => 'newsletter_subscribe']]),
      Field::make('text', 'button_text', 'button_text')->set_conditional_logic([['field' => 'action', 'value' => 'newsletter_subscribe']]),

Please have a look @Mooxdesign @ojohnny @moxxuk @benada002 :)