wpengine/wp-graphql-content-blocks

Interface field argument error in GraphQL IDE after update to WPGraphQL 1.26

traed opened this issue · 2 comments

I'm getting the following error since I updated WPGraphQL from version 1.24 to 1.26. I'm guessing they've done some changes to field definitions but since it's referring to editorBlocks I'm opening the issue here. Any idea what this might be?

      {
        "type": "GRAPHQL_DEBUG",
        "message": "Interface field argument \"NodeWithPostEditorBlocks.editorBlocks(flat:)\" expected to be of type \"Boolean\" but got \"Boolean\". Please ensure the field arguments match the interface field arguments or rename the argument.",
        "stack": [
          "/var/www/html/wp-content/plugins/wp-graphql/src/Type/WPInterfaceTrait.php:238",
          "/var/www/html/wp-content/plugins/wp-graphql/src/Type/WPInterfaceType.php:49",
          "/var/www/html/wp-content/plugins/wp-graphql/src/Registry/TypeRegistry.php:825",
          "/var/www/html/wp-content/plugins/wp-graphql/src/Registry/TypeRegistry.php:714",
          "/var/www/html/wp-content/plugins/wp-graphql/src/Registry/TypeRegistry.php:847",
          "/var/www/html/wp-content/plugins/wp-graphql/src/Registry/TypeRegistry.php:226",
          "/var/www/html/wp-content/plugins/wp-graphql/src/Registry/TypeRegistry.php:224",
          "/var/www/html/wp-content/plugins/wp-graphql/src/Registry/TypeRegistry.php:876",
          "/var/www/html/wp-content/plugins/wp-graphql/src/Registry/SchemaRegistry.php:44",
          "/var/www/html/wp-content/plugins/wp-graphql/src/WPGraphQL.php:704",
          "/var/www/html/wp-content/plugins/wp-graphql/src/Request.php:155",
          "/var/www/html/wp-content/plugins/wp-graphql/src/Router.php:461",
          "/var/www/html/wp-content/plugins/wp-graphql/src/Router.php:257",
          "/var/www/html/wp-includes/class-wp-hook.php:324",
          "/var/www/html/wp-includes/class-wp-hook.php:348",
          "/var/www/html/wp-includes/plugin.php:565",
          "/var/www/html/wp-includes/class-wp.php:418",
          "/var/www/html/wp-includes/class-wp.php:813",
          "/var/www/html/wp-includes/functions.php:1336",
          "/var/www/html/wp-blog-header.php:16",
          "/var/www/html/index.php:17"
        ]
      },

@theodesp @traed

any update on this issue. How to get around with this issue, wpgraphql made changes in their codebase.

@theodesp @traed

any update on this issue. How to get around with this issue, wpgraphql made changes in their codebase.

This is a current regression in WPGraphQL core, but iirc it's just a message and shouldn't affect the actual resolution of the query.