Use ISO codes instead of language IDs for fallback languages and translations (#13751)
* Use language ISO code for language fallback instead of language ID * Remove language and language ID from dictionary item and dictionary item translation * ADd unit test for dictionary item translation value extension * Make the internal service implementations sealed * Rename translation ISO code to be more explicit in its origin (Language) * Add breaking changes suppression * Handle save of invalid fallback iso code * Fixed test * Only allow non-UserCustomCulture's * Fixed and added tests * Rename ISO code validation method * Fix language telemetry test (create Swedish with the correct ISO code) --------- Co-authored-by: Bjarke Berg <mail@bergmania.dk>
This commit is contained in:
@@ -132,10 +132,12 @@ public class TelemetryProviderTests : UmbracoIntegrationTest
|
||||
{
|
||||
// Arrange
|
||||
var langTwo = _languageBuilder.WithCultureInfo("da-DK").Build();
|
||||
var langThree = _languageBuilder.WithCultureInfo("se-SV").Build();
|
||||
var langThree = _languageBuilder.WithCultureInfo("sv-SE").Build();
|
||||
|
||||
await LanguageService.CreateAsync(langTwo);
|
||||
await LanguageService.CreateAsync(langThree);
|
||||
var langTwoResult = await LanguageService.CreateAsync(langTwo);
|
||||
Assert.IsTrue(langTwoResult.Success);
|
||||
var langThreeResult = await LanguageService.CreateAsync(langThree);
|
||||
Assert.IsTrue(langThreeResult.Success);
|
||||
|
||||
IEnumerable<UsageInformation> result = null;
|
||||
|
||||
|
||||
Reference in New Issue
Block a user