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
Right now, whenever we need user information from a player, we need to pass along separate user information with the game or players, because users and players are stored separately in the store. Users should still be stored separately (normalized), but the selectors through which we get game information should return user information with the player, instead of just the user ID.
This could technically mean passing around larger objects, with duplicated information, but I don't think that's a real problem, and it would make the code much cleaner (we won't need players and playerUsers).
The text was updated successfully, but these errors were encountered:
Right now, whenever we need user information from a player, we need to pass along separate user information with the game or players, because users and players are stored separately in the store. Users should still be stored separately (normalized), but the selectors through which we get game information should return user information with the player, instead of just the user ID.
That is, instead of returning from the selector:
we return
This could technically mean passing around larger objects, with duplicated information, but I don't think that's a real problem, and it would make the code much cleaner (we won't need
players
andplayerUsers
).The text was updated successfully, but these errors were encountered: