TypeError when using sort/filters on allWpTermNode

[adel0559]

When querying a gatsby dev server (as in http://localhost:8000/__graphql when running gatsby develop) the server crashes if you query allWpTermNode with a filter or sort parameter. The error received looks as follows:

type.resolveType is not a function

  TypeError: type.resolveType is not a function
  
  - node-model.js:648 getFields
    [sitename]/[gatsby]/src/schema/node-model.js:648:29
  
  - node-model.js:661 resolveRecursive
    [sitename]/[gatsby]/src/schema/node-model.js:661:21
  
  - node-model.js:390 resolver
    [sitename]/[gatsby]/src/schema/node-model.js:390:38
  
  - nodes.ts:145 saveResolvedNodes
    [sitename]/[gatsby]/src/redux/nodes.ts:145:30
  
  - node-model.js:388 LocalNodeModel._doResolvePrepareNodesQueue
    [sitename]/[gatsby]/src/schema/node-model.js:388:13
  
  - node-model.js:351 
    [sitename]/[gatsby]/src/schema/node-model.js:351:22
  
  - task_queues.js:79 processTicksAndRejections
    internal/process/task_queues.js:79:11

Steps to reproduce

Query something like the following from a gatsby dev server connected to a wordpress site with some taxonomies added.

allWpTermNode(filter: {count: {gte: 1}}) {
    nodes {
      id
    }
  }

Expected result

The query return the expected terms.

Actual result

Server crashes with the error type.resolveType is not a function

Environment

gatsby: gatsby@next => 3.3.0-next.0
gatsby-background-image: latest => 1.5.0
gatsby-cli: latest => 3.1.0
gatsby-image: latest => 3.1.0
gatsby-plugin-breadcrumb: latest => 12.1.0
gatsby-plugin-compression-v2: latest => 0.1.0
gatsby-plugin-manifest: latest => 3.1.0
gatsby-plugin-offline: latest => 4.1.0
gatsby-plugin-postcss: latest => 4.1.0
gatsby-plugin-purgecss: latest => 6.0.0
gatsby-plugin-react-helmet: latest => 4.1.0
gatsby-plugin-s3: latest => 0.3.8
gatsby-plugin-sass: latest => 4.1.0
gatsby-plugin-sharp: latest => 3.1.2
gatsby-plugin-split-css: latest => 2.0.0
gatsby-plugin-typescript: latest => 3.1.0
gatsby-source-filesystem: latest => 3.1.0
gatsby-source-wordpress: latest => 5.1.0
gatsby-source-wordpress-menus: latest => 1.1.4
gatsby-transformer-sharp: latest => 3.1.0

npmGlobalPackages:
gatsby-cli: 3.0.0

Wordpress 5.7
wp-graphql 1.3.3
wp-gatsby 1.0.7

[adel0559]

Looking into this further there seems to be a problem using allWpTermNode in general if you have any custom taxonomies registered.

[jackonawalk]

Do you experience this same issue in Gatsby v2?

[henrikwirth]

I experience the same problem. It happens on all filters related to allWpTermNodes and also if I use them in some sort of connection like this:

query MyQuery {
  allWpProject(filter: {terms: {nodes: {elemMatch: {termTaxonomyId: {eq: 10}}}}}) {
    nodes {
      title
    }
  }
}

Running latest versions of all plugins.

[AlexMorrisonDev716]

Same issue here.

"gatsby": "^3.4.0",
"gatsby-gravityforms-component": "^3.1.0",
"gatsby-plugin-fontawesome-css": "^1.1.0",
"gatsby-plugin-image": "^1.4.0",
"gatsby-plugin-manifest": "^3.4.0",
"gatsby-plugin-netlify": "^3.4.0",
"gatsby-plugin-netlify-cache": "^1.2.0",
"gatsby-plugin-offline": "^4.4.0",
"gatsby-plugin-purgecss": "^6.0.1",
"gatsby-plugin-react-helmet": "^4.4.0",
"gatsby-plugin-react-svg": "^3.0.1",
"gatsby-plugin-remove-fingerprints": "^0.0.2",
"gatsby-plugin-sass": "^4.4.0",
"gatsby-plugin-sharp": "^3.4.0",
"gatsby-source-filesystem": "^3.4.0",
"gatsby-source-gravityforms": "^1.0.17",
"gatsby-source-wordpress": "^5.4.0",
"gatsby-transformer-sharp": "^3.4.0",

P.S. @henrikwirth Thank you so much for all the help your contributions have made on my latest project :)

[AlexMorrisonDev716]

I was able to resolve this issue by downgrading wp-graphql to 1.3.5 if anyone needs a quick fix.

[henrikwirth]

I was able to resolve this issue by downgrading wp-graphql to 1.3.5 if anyone needs a quick fix.

Interesting. So with v1.5.6 it breaks?

[jasonbahl]

@AlexMorrisonDev716 I think getting this to work by downgrading to WPGraphQL v1.3.5 must be a coincidence, because this issue was opened before WPGraphQL 1.3.5 was even released 🤔

[AlexMorrisonDev716]

@jasonbahl At least with my current combination of packages and plugins v1.3.5 is the last version of WPGraphQL that doesn't cause this error on build.

[tiggeymone]

Same error upgrading WpGraphQL. My query involves allWpContentNode:

kcFeed: allWpContentNode(
      filter: {
        contentType: { node: { name: { in: ["post", "news", "project"] } } }
      }
      sort: { fields: date, order: DESC }
    ) {
...

The error diseappears after downgrading WpGraphQL to 1.3.5

[AlexMorrisonDev716]

@tiggeymone Thank you for replicating this!