pageQuery doesn't reflect changes on its own

Description

I have a basic blog setup that is nearly identical to gatsby-theme-blog-core.

After adding a new post (markdown file) to a folder which is being used to incrementally build pages (/content/posts), I need to manually edit a pageQuery to reflect the changes. Even after building the site, the new post won’t show up. I recorded a short screen capture describing the issue.

Steps to reproduce

Follow instructions in this repo: https://github.com/vojtaholik/page-query-doesnt-reflect-changes#steps-to-reproduce-a-bug-with-pagequery-not-reflecting-changes

Expected result

pageQuery should reflect changes in the file tree on its own without needing to edit it.

Actual result

pageQuery didn’t reflect changes in file tree, even though they’re visible in graphiql.

May be related to something that isn’t hooked up in the data dependency tracking, specifically around the frontmatter values in MDX files?

Environment

  System:
    OS: macOS 10.15.5
    CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 10.16.0 - ~/.nvm/versions/node/v10.16.0/bin/node
    Yarn: 1.21.1 - ~/.nvm/versions/node/v10.16.0/bin/yarn
    npm: 6.9.0 - ~/.nvm/versions/node/v10.16.0/bin/npm
  Languages:
    Python: 2.7.16 - /usr/bin/python
  Browsers:
    Chrome: 83.0.4103.61
    Firefox: 76.0.1
    Safari: 13.1.1
  npmPackages:
    gatsby: ^2.22.15 => 2.22.15 
    gatsby-core-utils: ^1.3.3 => 1.3.3 
    gatsby-image: ^2.4.5 => 2.4.5 
    gatsby-link: ^2.4.3 => 2.4.3 
    gatsby-plugin-catch-links: ^2.3.3 => 2.3.3 
    gatsby-plugin-feed: ^2.5.3 => 2.5.3 
    gatsby-plugin-manifest: ^2.4.9 => 2.4.9 
    gatsby-plugin-mdx: ^1.2.13 => 1.2.13 
    gatsby-plugin-meta-redirect: ^1.1.1 => 1.1.1 
    gatsby-plugin-offline: ^3.2.7 => 3.2.7 
    gatsby-plugin-postcss: ^2.3.2 => 2.3.2 
    gatsby-plugin-react-helmet: ^3.3.2 => 3.3.2 
    gatsby-plugin-sharp: ^2.6.9 => 2.6.9 
    gatsby-plugin-twitter: ^2.3.2 => 2.3.2 
    gatsby-remark-copy-linked-files: ^2.3.3 => 2.3.3 
    gatsby-remark-images: ^3.3.8 => 3.3.8 
    gatsby-remark-prismjs: ^3.5.2 => 3.5.2 
    gatsby-remark-smartypants: ^2.3.2 => 2.3.2 
    gatsby-source-filesystem: ^2.3.8 => 2.3.8 
    gatsby-transformer-remark: ^2.8.13 => 2.8.13 
    gatsby-transformer-sharp: ^2.5.3 => 2.5.3 
  npmGlobalPackages:
    gatsby-cli: 2.8.15

[pieh]

Just used reproduction and can confirm it’s happening. Investigating now

(awesome bug report btw, repo and steps to reproduce are very clear!)

[vojtaholik]

I can confirm this is now fixed 🥳 thank you @pieh!