Salman Ahmed be2d616e34 Fix localisation use cases not falling back to default(LocalisableString) ... Previously such use cases have been returning `null` values just fine since `GetLocalisableString` was returning `LocalisableFormattableString`, and these null values were wrapped in `LocalisableString`s implicitly, therefore not requiring an explicit fallback string and `null` doesn't break anything.		2022-04-28 11:21:00 +03:00
..
DrawableTopScore.cs	Merge branch 'master' into adjust-beatmap-overlay	2020-02-21 09:52:44 +09:00
NoScoresPlaceholder.cs	Localise scoreboard	2021-08-16 13:38:57 +02:00
NotSupporterPlaceholder.cs	Use existing web localisation for most hardcoded strings	2022-04-20 16:31:11 -07:00
ScoreboardTime.cs	Move to extension method and revert logic to match previous implementation	2022-02-21 13:42:26 +09:00
ScoresContainer.cs	Resolve inspection issues	2022-04-14 13:11:11 +09:00
ScoreTable.cs	Obsolete BeatmapInfo.MaxCombo and suppress in usages	2022-03-20 16:30:29 +03:00
ScoreTableRowBackground.cs	Apply batch fixing of built-in types using var	2021-10-27 13:04:41 +09:00
TopScoreStatisticsSection.cs	Fix localisation use cases not falling back to default(LocalisableString)	2022-04-28 11:21:00 +03:00
TopScoreUserSection.cs	Fix missed null coalesce	2021-08-30 16:05:56 +09:00