Return list of Orgs for user as part of /users/me API

[SuaYoo]

#429 proposes showing a non superadmin user's default team as the first team returned from /archives (i.e. the archive they were invited to, or their first archive if the user self-registered.) The GET /api/users/me response could include the current user's team ID & name using the same logic to prevent the additional API call to show the user's current team.

[ikreymer]

Hm, i think first step is just to return all of the teams a user is part of, to reduce number of API requests, right?
Then, we'd need a way of setting / getting a default team, something like this:

• List all teams for user via user API endpoint
  - [ ] Support adding default team for user via API
  - [ ] List default team for user via API endpoint

Edit: for now, just listing all the Orgs a user is part of in /users/me

[SuaYoo]

Got it, I wasn't aware that teams and archives were going to be separate concepts on the backend, instead of archives = teams based on #394.

[ikreymer]

Got it, I wasn't aware that teams and archives were going to be separate concepts on the backend, instead of archives = teams based on #394.

Yes, teams = archives on the backend currently (possibly should rename?), but there's no concept of default team/archive at the moment.

[SuaYoo]

Per discord convo, getting the first (i.e. "default") team/archive is handled on the frontend right now but would be nice to move to the backend to reduce API calls:

• Return team with name and id from /users/me to immediately route users to the correct archive without having to wait for /archives to resolve (this can be the user's first team, cannot be changed by the user)
• Return a boolean like inMultipleTeams from /users/me to prevent additional call to /archives if a user isn't in multiple teams

[ikreymer]

Per discord convo, getting the first (i.e. "default") team/archive is handled on the frontend right now but would be nice to move to the backend to reduce API calls:

• Return team with name and id from /users/me to immediately route users to the correct archive without having to wait for /archives to resolve (this can be the user's first team, cannot be changed by the user)
• Return a boolean like inMultipleTeams from /users/me to prevent additional call to /archives if a user isn't in multiple teams

I was actually thinking it'd just be an array of teams, no guarantee about sorting order (but maybe based on creation time or alpha sorted?), and frontend can just remember selection / skip selection is only one entry?

[SuaYoo]

That makes sense, teams in /users/me response with team name and ID? IMO creation time sorted to start makes more sense since the frontend can sort by alpha if name is included