Update StaticQuery documentation

[iamhitarth]

To explicitly make it clear that StaticQuery should NOT be used on page components and doing so will result in a Loading (StaticQuery) message showing up on the page.

[gatsbybot]

Deploy preview for using-drupal ready!

Built with commit bfaa261

https://deploy-preview-6452--using-drupal.netlify.com

[gatsbybot]

Deploy preview for gatsbygram ready!

Built with commit bfaa261

https://deploy-preview-6452--gatsbygram.netlify.com

[gatsbybot]

Deploy preview for using-drupal ready!

Built with commit 089754b

https://deploy-preview-6452--using-drupal.netlify.com

[gatsbybot]

Deploy preview for gatsbygram ready!

Built with commit 089754b

https://deploy-preview-6452--gatsbygram.netlify.com

[gatsbybot]

Deploy preview for gatsbygram ready!

Built with commit 136cba4

https://deploy-preview-6452--gatsbygram.netlify.com

[gatsbybot]

Deploy preview for using-drupal ready!

Built with commit 136cba4

https://deploy-preview-6452--using-drupal.netlify.com

[LekoArts]

As far as I know Loading (StaticQuery) is just a bug and it's perfectly fine to use StaticQueries in page components. Where did you get that information?

[jquense]

yes, StaticQuery should be usable everywhere if it's not there is a bug we need to fix 👍

[iamhitarth]

@LekoArts @jquense in my Gatsby site that I migrated to v2 last night, using StaticQuery on a page component kept resulting in Loading (StaticQuery) as the only thing that would show up on the page.

See issue #6350 for more details.

Let me know if there is any additional information I can provide to help.

[LekoArts]

It‘s still a bug or a wrong use (two queries in the page component). If the latter you should try it with only one query at a time.

[m-allanson]

Thanks @iamhitarth! This sounds like it's a bug and not intended behaviour so I've updated the linked issue #6350 with a demo. I'm going to close this as we should fix the bug instead :)