Dan Balasescu 78e5e0eddd Refactor with a bit more null safety ... In particular I don't like the non-null assert around `GetCurrentItem()`, because there's no reason why it _couldn't_ be `null`. Consider, for example, if these panels are used in matchmaking where there are no items initially present in the playlist. The ruleset nullability part is debatable, but I've chosen to restore the original code here.		2025-02-11 12:20:09 +09:00
..
ParticipantPanel.cs	Refactor with a bit more null safety	2025-02-11 12:20:09 +09:00
ParticipantsList.cs	Replace MultiplayerRoomComposite with local bindings	2024-11-06 15:31:27 +09:00
ParticipantsListHeader.cs	Automated pass	2023-06-24 01:00:03 +09:00
StateDisplay.cs	Add visual display in participants list when availability is still being established	2023-06-28 16:02:46 +09:00
TeamDisplay.cs	Replace MultiplayerRoomComposite with local bindings	2024-11-06 15:31:27 +09:00