You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The frontend currently loads the user's whole profile in most cases, even if all it needs is the name + avatar. We discussed this at a few dev meetings, and for now I've implemented a GetLiteUser RPC that returns just the minimal info needed in the majority of cases in the backend. The main places where this does NOT work are the profile itself, and the map (that's a separate exercise).
In addition to the lite user RPC, there is also the GetLiteUsers RPC that gets many users: this allows fetching up to 200 users at a time in one backend call, which should significantly reduce the number of calls required e.g. when opening the map page.
This issue requires:
Creating a parallel useLiteUser(s) hook similat to the existing useUser(s) hook, and
Updating many uses of the latter hook to the new former hook.
The frontend currently loads the user's whole profile in most cases, even if all it needs is the name + avatar. We discussed this at a few dev meetings, and for now I've implemented a
GetLiteUser
RPC that returns just the minimal info needed in the majority of cases in the backend. The main places where this does NOT work are the profile itself, and the map (that's a separate exercise).In addition to the lite user RPC, there is also the
GetLiteUsers
RPC that gets many users: this allows fetching up to 200 users at a time in one backend call, which should significantly reduce the number of calls required e.g. when opening the map page.This issue requires:
useLiteUser(s)
hook similat to the existinguseUser(s)
hook, andcouchers/app/proto/api.proto
Lines 22 to 28 in 711efe7
The text was updated successfully, but these errors were encountered: