OneGraph / graphiql-explorer

Explorer plugin for GraphiQL
MIT License
907 stars 97 forks source link

Current project status #84

Open FluorescentHallucinogen opened 2 years ago

FluorescentHallucinogen commented 2 years ago

@sgrove @dwwoelfel

Is this project still maintained?

I see a lot of opened (and already reviewed) pull requests (e.g. #60, #49, etc.) for some reason are still not merged. Why?

What the future of this project after OneGraph was acquired by Netlify?

Will this project be refactored from one-single file to component files? Will it be migrated from Flow to TypeScript? Will it support theme customization?

Will this project be developed as a part of GraphiQL 2?

aggarwalnisha commented 2 years ago

Hi @sgrove @dwwoelfel,

This is a really helpful tool. Would love to know its current status.

We also see that there are some TODOs like supporting list arguments. Are there any plans to achieve them, or PRs are accepted for it? Single file to component files and Flow to Typescript will also be great to do.

Also, can we pass props to disable multiple queries and running mutations?

jonathanawesome commented 2 years ago

@FluorescentHallucinogen @aggarwalnisha We're working on GraphiQL v2 over here, including an Explorer-inspired GUI query builder. Join us on Discord!

tendant commented 2 years ago

It will be great to have new release with updated dependencies, even there is no new feature or bug fixes.

At least it can still be used by other projects.

Even with the release of v2, there will be a lot projects depending on v1 for a while.

haase1020 commented 1 year ago

@sgrove @dwwoelfel @jonathanawesome , I would also like to check on the status of this project. I would love to help if I can! I have a TypeScript version of the Explorer.js file, and would love to update dependencies and the code base. For example, you currently cannot upgrade to graphql v16 and without breaking the isDeprecated logic. Are there plans to make updates to this package? Is there any way to help?

acao commented 1 year ago

Here is my proposed future home of graphiql explorer:

https://github.com/graphql/graphiql/pull/3375

many more improvements to come, this is just a start one major caveat is that the git history is lost with this approach. but it would make it much easier for us to maintain

klippx commented 7 months ago

@acao The PR you linked to was merged to main. But what happened after that? It seems to have been removed since... Did it not make sense to absorb this abandonded project into the graphiql monorepo?

acao commented 7 months ago

it was merged into this branch so it hasn't been merged to main yet. we were encouraged to redo the whole thing but I'm not afraid of large, gradual rewrites!