-
Notifications
You must be signed in to change notification settings - Fork 10.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(examples): GraphQL reference codesandbox issue #10807
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could probably just refactor the blog template slightly--but this works just as well.
Nice; thank you!
Codesandbox doesn't have access to that file (I think) |
It wasn't published yet I think |
Ah, I see. However I think Codesandbox will only restart the dev server (instance) if something changed on the repo. So if we don't change the PATH_PREFIX we'd need to change something else to trigger a new run. |
We'd need to upgrade to the version of gatsby that contains this change--so maybe we do that in this PR? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💪 Thanks!
Didn't work out as expected, |
@LekoArts I'm not sure the change has been published yet. The |
I just published .84 with the change |
## Description A version of Gatsby with the correct fix has been published, this is the same as #10807
* Remove PATH_PREFIX from graphql-reference-example * update package instead
## Description A version of Gatsby with the correct fix has been published, this is the same as gatsbyjs#10807
Codesandbox apparently fails on that