Feature Request: Expose graphql source query.

Summary

At prismic we have a use-case for re-running a graphql source query during runtime and would like to know if there is an already existing solution to exposing the source-query or make a feature request.

Our main use-case is to re-run the query at run-time in-order to make preview work. see example below:

import { StaticQuery, graphql } from 'gatsby';
import { withPreview } from 'gatsby-source-prismic-graphql';

const articlesQuery = graphql`query { prismic { ... } }`;

export const Articles = () => (
  <StaticQuery query={articlesQuery} render={withPreview(data => { ... }, articlesQuery)} />
);

Basic example

Our current solution involves patching the babel-plugin-remove-graphql with this https://github.com/birkir/gatsby-source-graphql-universal/blob/master/scripts/patches/babel-plugin-remove-graphql-queries.patch But this patch breaks useStaticQuery site-wide.

Motivation

Why are we doing this?

• We do this to provided a better user experience when using our preview feature

What use cases does it support?

• Fetching and using data from a content management service client side.

What is the expected outcome?

• Alternative methods to achieve these same goals.
• or expose the graphql query source so it can be re-run

We would be happy to make a PR to enable this feature.

[MarcMcIntosh]

PR https://github.com/gatsbyjs/gatsby/pull/23423

[github-actions[bot]]

Hey again!

It’s been 30 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 reopen 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! 💪💜