Bug in localization?

[svenbaus]

Hello,
I'm using the ITextLocalizer and I'm facing a strange behaviour, maybe a bug. First my setup:

I get the localized resourced for ITextLocalizer<ProcessStepMessage> _processStepMessageLocalizer in my object ITextLocalizer<ProcessStep> _processStepLocalizer. So I think the search for the resource has a bug or what am I doing wrong?

[stsrki]

From the screenshots, I cannot find what might be the cause of the problem. Is there any chance you could prepare us a small project to reproduce the issue on our side?

[svenbaus]

So I've been able to get a small example running that demonstrates the problem. Just unzip it, run it and navigate to "/process/details/4c6ab2d9-67b3-4f1f-8ef7-30b783561cd2" (or any other guid), the data are hardcoded. Afterwards select the step and you will see my problem.

example.zip

[stsrki]

I found the problem. We have the wrong check Contains( $"Resources.Localization.{resourceName}" ) so when there are multiple folders that starts the same all of them will be retrieved.

protected virtual string[] GetLocalizationResourceNames( Assembly assembly, string resourceName )
{
  return assembly.GetManifestResourceNames()
+    .Where( r => r.Contains( $"Resources.Localization.{resourceName}" ) && r.EndsWith( ".json" ) )
    .ToArray();
}

I will convert this to issue now.

[svenbaus]

Ok, thanks :). Is there any idea, in which release this bug will be resolved?

[stsrki]

It will be in 1.0.7. In the next week or two, I would guess.

[svenbaus]

Perfect, thanks for pointing out :).