Context
As the title says: on the /members page, each list item calls the userById endpoint. This is a lot of individual calls and should not be necessary as the list item already loads the displayed info.
- The original goal of having userById endpoint in each list item is so when we disable/enable a user, their status updates without having to re-render the entire list. We should keep this behavior
- We just need a way to seed the query with the passed in data at the beginning and make sure it stays valid with this data.
Testing
- Make sure when opening
/members there is not a massive backend call for all the users info.
- Make sure when updating the disabled status of a member, the individual row updates and without re-rending the entire list