hoppscotch
hoppscotch copied to clipboard
hoppscotch
[feature]: Team Collections for GraphQL
Is there an existing issue for this?
- [X] I have searched the existing issues
Summary
Team collections should be available for GraphQL requests in exactly the same way as for REST requests. Currently, only private collections seem to be available in GraphQL mode.
Why should this be worked on?
Team collections are just as relevant for GraphQL requests as for REST requests. The current discrepancy between the two modes is confusing to users.
I would be happy to help on that one. Perhaps for the maintainer - how would you like this work to be done? I can see that the model splits the logic between REST and GraphQL, would you like some refactor to make some generic solution or would you prefer something different? Perhaps if you have any guidelines, I'd be happy to get started with that one!
@acolombier Teams codebase is not open source yet so I don't think you will be able to help with it. But it is something we are focusing on and will be pushing in the coming weeks.
Thanks for the update @AndrewBastin Is there any plan to make the teams codebase open source too?
@acolombier we are working on that. It's just there are many moving pieces we are still figuring out regarding our business goals and such. Hopefully we will figure something out eventually and get an open source backend implementation running by next year.
Would really like to get this as we can't implement locally in our corp environment without team collaboration. Otherwise we have to pay for postman.
Team Collections on GraphQL is currently deferred as a low priority and won't most probably happen until next year.
We will be updating this thread once we are ready to work on this.
Hi, Providing team collaboration on GraphQL is on our current roadmap. We have not started working on this yet, but we aim to release it sometime in the middle of this year.
