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

Updated GraphiQL playground 2.0.7 -> 3.0.1 and react 17.0.2 -> 18.2.0 #2713

Merged

Conversation

UnAfraid
Copy link
Contributor

Addressing #2712

I have:

  • Added tests covering the bug / feature (see testing)
  • Updated any relevant documentation (see docs)

@coveralls
Copy link

coveralls commented Jul 14, 2023

Coverage Status

coverage: 75.738% (+0.05%) from 75.692% when pulling c70bd6f on UnAfraid:feature/update-graphiql-playground into 7880739 on 99designs:master.

@UnAfraid UnAfraid force-pushed the feature/update-graphiql-playground branch from 596b6a0 to c70bd6f Compare July 14, 2023 11:28
@UnAfraid UnAfraid changed the title Updated GraphiQL playground 2.0.7 -> 3.0.1 and react 17 -> 18 Updated GraphiQL playground 2.0.7 -> 3.0.1 and react 17.0.2 -> 18.2.0 Jul 14, 2023
@StevenACoffman StevenACoffman merged commit 8c378e6 into 99designs:master Jul 14, 2023
@StevenACoffman
Copy link
Collaborator

Thanks!

@UnAfraid UnAfraid deleted the feature/update-graphiql-playground branch July 14, 2023 12:45
@UnAfraid
Copy link
Contributor Author

UnAfraid commented Jul 14, 2023

Do we need unit/integration test that covers the playgrounds actually load (making sure integrity checks are passing)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants