Users blocking now rely on UUID rather than ID

This way, if a user A blocks another user B, if user B refreshes the browser or leaves and re-enters the room, user B will still be blocked.
As a side effect, this allows us to completely remove the "sockets" property in the SocketManager on the Pusher.
This commit is contained in:
David Négrier 2021-07-07 11:24:51 +02:00
parent 28e4f59e50
commit 34cb0ebf39
15 changed files with 143 additions and 141 deletions

View file

@ -62,7 +62,7 @@ message WebRtcSignalToServerMessage {
}
message ReportPlayerMessage {
int32 reportedUserId = 1;
string reportedUserUuid = 1;
string reportComment = 2;
}
@ -158,6 +158,7 @@ message UserJoinedMessage {
PositionMessage position = 4;
CompanionMessage companion = 5;
string visitCardUrl = 6;
string userUuid = 7;
}
message UserLeftMessage {
@ -285,6 +286,7 @@ message UserJoinedZoneMessage {
Zone fromZone = 5;
CompanionMessage companion = 6;
string visitCardUrl = 7;
string userUuid = 8;
}
message UserLeftZoneMessage {