PouryaKit.Localization

A Module's messages in English and Persian. A Feature injects IStringLocalizer<T> for a type of its own and reads each message by its key, from .resx files beside that type's file. Each HTTP request runs in English or Persian as its client's Accept-Language header names, in English otherwise, and that culture flows through the Gateway into the Operation's handlers.

InstallCopy Anchor Link

dotnet add package PouryaKit.Localization --prerelease

When to use itCopy Anchor Link

• A Module's messages must read in English and Persian.
• You read the request culture from the client's language header.
• A cached query must answer each culture in its own language.

It is optional and references only PouryaKit.Cqrs and the ASP.NET Core shared framework. A Host that answers in English alone leaves it out.

Quick startCopy Anchor Link

Register it in the Composition Root of each Module that writes localized messages:

module.AddPouryaKitLocalization();

Put the messages beside a marker type, and read each one by its key, as the Kit's tests do:

internal sealed class StubMessages;

internal sealed record GreetQuery : Query<string>;

internal sealed class GreetQueryHandler(IStringLocalizer<StubMessages> messages)
    : QueryHandler<GreetQuery, string>
{
    public override Task<Result<string>> Handle(
        GreetQuery query,
        CancellationToken cancellationToken
    ) => Task.FromResult<Result<string>>(messages["Greeting"].Value);
}

What you getCopy Anchor Link

• The shared framework's IStringLocalizer<T>, with no extra NuGet package.
• The request culture applied ahead of the Host's own middleware, with nothing to call in its pipeline.
• The culture carried through the Gateway into the Operation's handlers.

Learn moreCopy Anchor Link

• Localization
• A Module writing localized messages
• What the Kit guarantees
• Limits