Skip to content

Conversation

@ynnoj
Copy link
Contributor

@ynnoj ynnoj commented Feb 17, 2021

Build and query nodes from multiple Content Stages.

Fixes #135.

@ynnoj ynnoj self-assigned this Feb 17, 2021
@ynnoj ynnoj requested a review from notrab February 17, 2021 16:26
@gatsby-cloud
Copy link

gatsby-cloud bot commented Feb 17, 2021

Gatsby Cloud Build Report

gatsby-source-graphcms

🎉 Your build was successful! See the Deploy preview here.

Build Details

View the build logs here.

🕐 Build time: 18s

Performance

Lighthouse report

Metric Score
Performance 💚 100
Accessibility 💚 92
Best Practices 💚 100
SEO 🔶 73

🔗 View full report

@ynnoj ynnoj marked this pull request as ready for review February 17, 2021 16:48
notrab
notrab previously approved these changes Feb 17, 2021
Copy link
Contributor

@notrab notrab left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Amazing! This looks great.

It might be worth mentioning somewhere that the API token is tightly bound to your content stages. So if you attempt to use the PUBLISHED stage, and your token is only scoped to DRAFT, you're gonna have problems.

@ynnoj ynnoj enabled auto-merge (squash) February 18, 2021 08:33
@notrab
Copy link
Contributor

notrab commented Feb 18, 2021

lgtm

Co-authored-by: Jamie Barton <jamie@notrab.dev>
@ynnoj ynnoj merged commit b5f6b2d into main Feb 18, 2021
@ynnoj ynnoj deleted the feat/build-nodes-multiple-stages branch February 18, 2021 08:41
@github-actions
Copy link

🎉 This PR is included in version 2.3.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Filter content stage accordingly to the API token settings

3 participants