-
Notifications
You must be signed in to change notification settings - Fork 97
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
Current project status #84
Comments
Hi @sgrove @dwwoelfel, This is a really helpful tool. 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? Also, can we pass props to disable multiple queries and running mutations? |
@FluorescentHallucinogen @aggarwalnisha We're working on GraphiQL v2 over here, including an Explorer-inspired GUI query builder. Join us on Discord! |
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. |
@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 |
Here is my proposed future home of graphiql explorer:
many more improvements to come, this is just a start |
@acao The PR you linked to was merged to |
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! |
@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?
The text was updated successfully, but these errors were encountered: