[gatsby-plugin-wordpress] 'WPGraphQL menu data' not merging properly with the 'Gatsby schema & Node model'

[Srishtichambail]

Description

WPGraphQL menu data not merging properly with the Gatsby schema & Node model. Not able to see menu data when querying allWpMenu or allWpMenuItem. Menu items are visible in Wordpress GraphiQL IDE but not in Gatsby GraphiQL IDE.

Steps to reproduce

• Start with gatsby-starter-wordpress-blog.
• gatsby-node.js

  
  const path = require('path')
  const chunk = require('lodash/chunk')

// This is a simple debugging tool // dd() will prettily dump to the terminal and kill the process // const { dd } = require('dumper.js')

/**

• exports.createPages is a built-in Gatsby Node API.
• It's purpose is to allow you to create pages for your site! 💡

• See https://www.gatsbyjs.com/docs/node-apis/#createPages for more info. */ exports.createPages = async gatsbyUtilities => { // Query our posts from the GraphQL server await createAllSitePages(gatsbyUtilities); const posts = await getPosts(gatsbyUtilities)

  // If there are no posts in WordPress, don't do anything if (!posts.length) { return }

  // If there are posts, create pages for them await createIndividualBlogPostPages({ posts, gatsbyUtilities })

  // And a paginated archive await createBlogPostArchive({ posts, gatsbyUtilities }) }

const createAllSitePages = async (gatsbyUtilities) => {

const pageTemplate = path.resolve('./src/templates/page.js') const pages = await gatsbyUtilities.graphql(' { allWpPage { edges { node { id title content slug } } } } ') return Promise.all( pages.data.allWpPage.edges.map(edge => { console.log('page created:', edge.node.title, edge.node.slug); gatsbyUtilities.actions.createPage({ path: '/${edge.node.slug}/', component: pageTemplate, context: { title: edge.node.title, }, }) }) ) }

/**

• This function creates all the individual blog pages in this site */ const createIndividualBlogPostPages = async ({ posts, gatsbyUtilities }) => Promise.all( posts.map(({ previous, post, next }) => // createPage is an action passed to createPages // See https://www.gatsbyjs.com/docs/actions#createPage for more info gatsbyUtilities.actions.createPage({ // Use the WordPress uri as the Gatsby page path // This is a good idea so that internal links and menus work 👍 path: post.uri,

  // use the blog post template as the page component
  component: path.resolve('./src/templates/blog-post.js'),
  
  // 'context' is available in the template as a prop and
  // as a variable in GraphQL.
  context: {
    // we need to add the post id here
    // so our blog post template knows which blog post
    // the current page is (when you open it in a browser)
    id: post.id,
  
    // We also use the next and previous id's to query them and add links!
    previousPostId: previous ? previous.id : null,
    nextPostId: next ? next.id : null,
  },

  }) ) )

/**

• This function creates all the individual blog pages in this site / async function createBlogPostArchive({ posts, gatsbyUtilities }) { const graphqlResult = await gatsbyUtilities.graphql(/ GraphQL */ ' { wp { readingSettings { postsPerPage } } } ')

  const { postsPerPage } = graphqlResult.data.wp.readingSettings

  const postsChunkedIntoArchivePages = chunk(posts, postsPerPage) const totalPages = postsChunkedIntoArchivePages.length

  return Promise.all( postsChunkedIntoArchivePages.map(async (_posts, index) => { const pageNumber = index + 1

  const getPagePath = page => { if (page > 0 && page <= totalPages) { // Since our homepage is our blog page // we want the first page to be "/" and any additional pages // to be numbered. // "/blog/2" for example return page === 1 ? '/' : '/blog/${page}' }

  return null

  }

  // createPage is an action passed to createPages // See https://www.gatsbyjs.com/docs/actions#createPage for more info await gatsbyUtilities.actions.createPage({ path: getPagePath(pageNumber),

  // use the blog post archive template as the page component
  component: path.resolve('./src/templates/blog-post-archive.js'),
  
  // 'context' is available in the template as a prop and
  // as a variable in GraphQL.
  context: {
    // the index of our loop is the offset of which posts we want to display
    // so for page 1, 0 * 10 = 0 offset, for page 2, 1 * 10 = 10 posts offset,
    // etc
    offset: index * postsPerPage,
  
    // We need to tell the template how many posts to display too
    postsPerPage,
  
    nextPagePath: getPagePath(pageNumber + 1),
    previousPagePath: getPagePath(pageNumber - 1),
  },

  }) }) ) }

async function getPosts({ graphql, reporter }) { const graphqlResult = await graphql(/ GraphQL / ' query WpPosts {

Query all WordPress blog posts sorted by date

  allWpPost(sort: { fields: [date], order: DESC }) {
    edges {
      previous {
        id
      }

      # note: this is a GraphQL alias. It renames "node" to "post" for this query
      # We're doing this because this "node" is a post! It makes our code more readable further down the line.
      post: node {
        id
        uri
      }

      next {
        id
      }
    }
  }
}

')

if (graphqlResult.errors) { reporter.panicOnBuild( 'There was an error loading your blog posts', graphqlResult.errors ) return }

return graphqlResult.data.allWpPost.edges }

- menu query

allWpMenu { edges { node { menuItems { nodes { label } } } } }

### Expected result

Query should return all menu items

### Actual result

No menu item is returned

### Environment

System:
    OS: Windows 10 10.0.18362
    CPU: (4) x64 Intel(R) Core(TM) i3-6100U CPU @ 2.30GHz
  Binaries:
    Node: 12.18.0 - C:\Program Files\nodejs\node.EXE
    npm: 6.14.4 - C:\Program Files\nodejs\npm.CMD
  Languages:
    Python: 2.7.15 - /c/Users/Srishti/.windows-build-tools/python27/python
  Browsers:
    Edge: Spartan (44.18362.1.0)
  npmPackages:
    gatsby: ^2.30.1 => 2.32.2
    gatsby-image: ^2.9.0 => 2.11.0
    gatsby-plugin-manifest: ^2.10.0 => 2.12.0
    gatsby-plugin-offline: ^3.8.0 => 3.10.0
    gatsby-plugin-react-helmet: ^3.8.0 => 3.10.0
    gatsby-plugin-sharp: ^2.12.0 => 2.14.1
    gatsby-source-filesystem: ^2.9.0 => 2.11.0
    gatsby-source-wordpress: ^4.0.3 => 4.0.3
    gatsby-transformer-sharp: ^2.9.0 => 2.12.0
  npmGlobalPackages:
    gatsby-cli: 2.19.2

[Srishtichambail]

Any update on this?

[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! 💪💜

[github-actions[bot]]

Hey again!

It’s been 60 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it. Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m HUMAN_EMOTION_SORRY. Please feel free to comment on this issue or create a new one if you need anything else. 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 again for being part of the Gatsby community! 💪💜