I noticed about 8 months ago we got rid of the resolver for Organization.teams & more recently we we added some new fields that can get queried. I hit a bug because Organization.teams is valid GQL, but teams doesn't have a resolver!

My tension here with having viewerTeams, allTeams, publicTeams is that these 3 lists can get out of sync with each other. E.g. if a team gets added, the client has to be sure to fetch that team under all 3 lists or it will be missing from 1 list but not the others! Less importantly, it triples the amount of data sent because if I have 100 teams, then I'll have to send data for300 teams, 100 for each list.

Instead, since all 3 return a list of teams that the viewer can access, I propose we re-instate the Organization.teams resolver & get rid of these 3. Then, to determine if it's a public team that the user isn't on, we just check Team.isViewerOnTeam.

@nickoferrall since you worked on this recently I wanted to get your thoughts on this direction

AC

• viewerTeams, allTeams, publicTeams are removed from the GraphQL API
• teams is re-added to the GraphQL API
• filtering is performed client-side based on if the viewer in on that team