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

Support GraphiQL #439

Closed
LoicPoullain opened this issue May 31, 2019 · 6 comments
Closed

Support GraphiQL #439

LoicPoullain opened this issue May 31, 2019 · 6 comments

Comments

@LoicPoullain
Copy link
Member

Issue

GraphiQL is in-browser IDE for exploring GraphQL. It would be useful to have it in Foal to explore and test our GraphQL APIs

Possible solution

Add a new package named @foal/graphiql

@darekaze
Copy link

Instead of iGraphQL, why not GraphQL Playground? I feel the later will have a better dev experience

@LoicPoullain
Copy link
Member Author

This can be done. I'm open to discussion about the pros and cons of choosing GraphQL Playground over GraphiQL

GraphiQL seems to be more widely used at the moment and relies on fewer direct and indirect dependencies. Is there a specific reason why you would prefer to use G-Playground over GraphiQL?

https://www.npmjs.com/package/graphql-playground-react
https://www.npmjs.com/package/graphiql

https://snyk.io/test/npm/graphql-playground-react
https://snyk.io/test/npm/graphiql

@darekaze
Copy link

darekaze commented Oct 15, 2019

Quoted from the graphql-playground project:

How is this different from GraphiQL?

GraphQL Playground uses components of GraphiQL under the hood but is meant as a more powerful GraphQL IDE enabling better (local) development workflows. Compared to GraphiQL, the GraphQL Playground ships with the following additional features:

  • Interactive, multi-column schema documentation
  • Automatic schema reloading
  • Support for GraphQL Subscriptions
  • Query history
  • Configuration of HTTP headers
  • Tabs

Yeah, I know it's big, but it will be an opt-in dev dependency and it won't affect building for production.

To list out some features I like it more cause it support subscription out-of-the-box, and get history and tabs features which I found them very useful.

Foal is already good in dev experience imo, and I think graphql-playground can make the dev experience in GraphQl even better. If there are any better options, I'm all hear.

@agustif
Copy link

agustif commented Mar 9, 2021

+1 for GraphQL Playground for me, I guess both are good options if (optional) but, maybe graphiql could come as dfault and playground be an extra command to install (because it's bigger, idk)

@LoicPoullain LoicPoullain mentioned this issue Apr 16, 2021
7 tasks
@LoicPoullain
Copy link
Member Author

According to this issue (graphql/graphql-playground#1143), GraphQL Playground will become a GraphiQL preset in the future and its repo will be archived. This is why Foal will use GraphiQL as default GraphQL viewer.

@LoicPoullain LoicPoullain mentioned this issue Apr 16, 2021
5 tasks
@LoicPoullain
Copy link
Member Author

Feature added in v2.3

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

No branches or pull requests

3 participants