Localization - async and CallerArgumentExpression

[cx-seibel]

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

Using async methods and provide arguments like ILogger does

Describe the solution you'd like

Hi,
I just wonder why IStringLocalizer or IStringLocalizer< T > does not support async methods since getting translations is usually from filesystem or database and can be async.
But more importent, it would be great using CallerArgumentExpression for arguements.
Instead of providing a string like "My name is {0} and my age is {1}"
we could use "My name is {Name} and my age is {Age}" like Ilogger does.

Thank you all

Additional context

(https://youtu.be/MHIheQ2_Yb4?t=324)

[hishamco]

I might agree to support async methods. I did a few implementations, including JsonStringLocalizer and EFStringLocalizer, where it required me to use async

Also, I remembered there's a new case where I introduced my own APIs when I worked in Orchard Core Contrib, @DamianEdwards, your thoughts?

[hishamco]

Any updates on this?

[captainsafia]

@hishamco No updates on this at the moment. This change will likely require an API proposal and design proposal to go through and some more interest in the feature via upvotes on the issue.

[hishamco]

Thanks for clarification @captainsafia

[hishamco]

My vote for supporting async version, should I upvote on this issue or open a separate issue for Async only

[captainsafia]

My vote for supporting async version, should I upvote on this issue or open a separate issue for Async only

You can upvote this one.