ACF Post Object in a Repeater Field - cannot query field

[kodepine]

I've got a Post Object, in a repeater field - that fetches data from a custom post type.
No data is returned i graphql

I've tested with a text-field, and thats returns data just fine.

[jasonbahl]

@kodepine do you have the engine post type set to Show in GraphQL?

[kodepine]

@kodepine do you have the engine post type set to Show in GraphQL?

Like this?

[jasonbahl]

Ya. Hmm. This looks all correct on quick glance. I'll need to dig in.

One note: On the Post Type registry, you shouldn't need graphql_singular_name and graphql_plural_type, just graphql_single_name and graphql_plural_name

[kodepine]

Thank you. Let me know if you want me to test anything.

I've changed the register_post_type accordingly

[jasonbahl]

@kodepine I'm not sure my answer this late will be helpful, but I'll add some insight anyway.

I believe the issue here is that the Post Object field returns a Union (and will be changing to an Interface in v0.6.0 (#262).

To reproduce, I did the following:

Registered the Post Type:

add_action( 'init', function() {

	register_post_type( 'engineCpt', [
		'show_ui' => true,
		'label' => 'Engine',
		'show_in_graphql' => true,
		'graphql_single_name' => 'EngineCpt',
		'graphql_plural_name' => 'EngineCpts'
	] );

});

Published a Post in the Post Type:

Created the Field

I created a Post Object field in my field group and named it sEngine.

Update Post with Engine Selected

Query the field in GraphQL

v0.5.2

In WPGraphQL for ACF v0.5.2 and older, the Post Object field type returns a Union in the GraphQL Schema, which means that you must specify what fields you want based on the Type that's returned.

Because the Post could be of any Post Type, it's not possible to know until runtime which Type will be returned, so you specify in the query like so:

...
{
  post(id: 2179, idType: DATABASE_ID) {
    id
    databaseId
    postTest {
      sengine {
        __typename
        ... on EngineCpt {
          id
          title
        }
      }
    }
  }
}

And would get results like so:

v0.6.0

In v0.6.0 (#262) this will be changing a bit. The Post Object field type will return a Connection to the ContentNode interface, instead of a PostObjectUnion, so you could query like so:

{
  post(id: 2179, idType: DATABASE_ID) {
    id
    databaseId
    postTest {
      sEngine {
        node {
          __typename
          id
          ... on EngineCpt {
            id
            title
          }
        }
      }
    }
  }
}