Skip to content
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(gatsby-graphiql-explorer): Use upstream exporter package #36966

Merged
merged 1 commit into from
Nov 7, 2022

Conversation

LekoArts
Copy link
Contributor

@LekoArts LekoArts commented Nov 4, 2022

Description

Use my upstream PR graphql/graphiql#2758 instead of vendoring it. Tested it locally with gatsby-dev, looks all the same.

Also updated the snippets a little bit.

Related Issues

[ch57842]

@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Nov 4, 2022
@LekoArts LekoArts added topic: GraphQL Related to Gatsby's GraphQL layer and removed status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer labels Nov 4, 2022
@tyhopp tyhopp merged commit 0ad6314 into master Nov 7, 2022
@tyhopp tyhopp deleted the graphiql-update branch November 7, 2022 01:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: GraphQL Related to Gatsby's GraphQL layer
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants