In this particular case guarding with `.IsNull()` makes no sense, as the `Trigger` is supplied in constructor and cannot feasibly be null. Doing that only makes sense in scenarios where BDL / dependency injection is involved.
IHasRecordingHandler.Recorder
FilterCriteria
KeyCounterController
RulesetInputManager
Localise multiplayer countdown buttons
Use beatmap cache to populate beatmap information in tournament client
Update login overlay appearance to match new designs
Fix `OpenUserProfile` links having multiple argument types
FillFlowContainer
LoginPanel
LoginOverlay
Fix tournament chat potentially crashing due to null current match
GetResultSafely()
permitNulls
Early-returning from ctors feels pretty bad. Also saves on some nested accesses.
#nullable disable
LadderInfo
This reverts commit 0dced46100.
0dced46100
As discussed, this would bring more problems that anything. Refs: 4c39708, f83a4f4
4c39708
f83a4f4
Only require exit confirmation when there are background operations