gatsby-source-wordpress: Filter for WPGraphQL for Advanced Custom Fields - Post Object Field - missing

[hasslarp]

Preliminary Checks

• This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/gatsbyjs/gatsby/issues
• This issue is not a question, feature request, RFC, or anything other than a bug report directly related to Gatsby. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions

Description

When adding a post object link in ACF the field can be queried just fine, but it can't be filtered on.

Using the following plugins in wordpress:
Advanced Custom Fields
WP Gatsby
WP GraphQL
WPGraphQL for Advanced Custom Fields

Se reproduction link for a stack overflow question on the subject.

Reproduction Link

https://stackoverflow.com/questions/68962977/filtering-on-an-acf-post-object-field-in-wordpress-in-gatsby-and-graphql

Steps to Reproduce

1. Install plugins in wordpress and set up wordpress as source with gatsby-source-wordpress
2. Create a new field group on pages with ACF and add a "Post Object" field that links to a page
3. Make sure everything is set to show in GraphQL
4. Have two pages and make on link to the other with the created "Post Object" field
5. Build the project in gatsby and try to filter on the linked page

Expected Result

Just as you are able to filter on, for example, the WpParent field, you should be able to filter on the linked page.

Actual Result

The post object field isn't even present in the list of available filters.

Environment

System:
    OS: macOS 11.5.2
    CPU: (4) x64 Intel(R) Core(TM) i5-7267U CPU @ 3.10GHz
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 15.8.0 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 7.5.0 - /usr/local/bin/npm
  Languages:
    Python: 2.7.16 - /usr/bin/python
  Browsers:
    Chrome: 93.0.4577.63
    Safari: 14.1.2
  npmPackages:
    gatsby: ^3.3.0 => 3.11.1 
    gatsby-image: ^3.3.0 => 3.11.0 
    gatsby-plugin-image: ^1.11.0 => 1.11.0 
    gatsby-plugin-manifest: ^3.3.0 => 3.11.0 
    gatsby-plugin-offline: ^4.3.0 => 4.11.0 
    gatsby-plugin-react-helmet: ^4.3.0 => 4.11.0 
    gatsby-plugin-sharp: ^3.11.0 => 3.11.0 
    gatsby-plugin-sitemap: ^4.9.0 => 4.9.0 
    gatsby-source-filesystem: ^3.3.0 => 3.11.0 
    gatsby-source-wordpress: ^5.3.0 => 5.11.0 
    gatsby-transformer-sharp: ^3.11.0 => 3.11.0 
  npmGlobalPackages:
    gatsby-cli: 3.8.0

Config Flags

No response

[TylerBarnes]

Hi @hasslarp , this isn't actually a bug but is a feature request. The WPGraphQL and Gatsby schemas are 2 separate schemas and filtering just hasn't been implemented in the Gatsby schema programatically yet.

[hasslarp]

Hi @hasslarp , this isn't actually a bug but is a feature request. The WPGraphQL and Gatsby schemas are 2 separate schemas and filtering just hasn't been implemented in the Gatsby schema programatically yet.

@TylerBarnes Oki. I figured that it was supposed to work analogous to the WpParent field. Also since I could filter on other ACL field types, that post object fields should be filterable as well.

But if it's not a bug, it's a feature request. :)

[github-actions[bot]]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here.
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜