mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #2013] [feature]: Team Collections for GraphQL #656
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#656
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @s-go on GitHub (Dec 13, 2021).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2013
Is there an existing issue for this?
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.
@acolombier commented on GitHub (Dec 17, 2021):
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!
@AndrewBastin commented on GitHub (Dec 18, 2021):
@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.
@acolombier commented on GitHub (Dec 18, 2021):
Thanks for the update @AndrewBastin
Is there any plan to make the teams codebase open source too?
@AndrewBastin commented on GitHub (Dec 18, 2021):
@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.
@justinelliss-coinme commented on GitHub (Mar 24, 2022):
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.
@denes16 commented on GitHub (Oct 20, 2022):
Any news on this?
@AndrewBastin commented on GitHub (Oct 22, 2022):
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.
@anabastos commented on GitHub (Mar 22, 2023):
Any updates on the issue?
@Leon-Luu commented on GitHub (Mar 11, 2024):
Any updates on this?
@venkatayedidasv commented on GitHub (Mar 11, 2024):
had same challenge, will be great to get update on this ?
@thetronjohnson commented on GitHub (Mar 11, 2024):
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.
@desutha commented on GitHub (Nov 25, 2025):
Hey guys! Really hope this gets fixed soon. I’m obsessed with this app.