honor type-annotations in parameter-declarations

[earloc]

As a developer, I want the source-generator to honor primitive type-declarations in parameter-expressions of a ResX-File´s key value, to let the generator produce better typin gs while generating wrapper-methods, in order to ensure that I pass the correct value to a translation.

[earloc]

Keys of a ResX-File might introduce a type-annotation, that get´s honored during code generation
Something like
Hello, {userName:string} might end up as an extension-method with the following signature:

public static string Hello__userName(..., string userName)...

instead of always falling back to object, as the current implementation does (and btw is the most annoying missing link to just use vanilla IStringLocalizer<T>-Index access ):

public static string Hello__userName(..., object userName)...

Utilizing existing formatting-annotations as for string.Format() might be a good idea as well. But solely utilizing these feels a bit of a too steep learning-curve for people just looking for a drop-in-enhancement to get a more typed and manageable acceess to localizables.

[earloc]

initial design should honor:

• int
• double
• string
• DateTime
• DateTimeOffset

---

• bool <- should this provide a built-in lookup or similar for true/false/null, on/off/partial, yes/no/maybe, enabled/disabled/dunno, wahr/falsch/vielleicht, ja/nein/keine Ahnung?

More to consider:
What about Nullable<T>s of these types. Should there be some kind of fallback-resolution in a sensible way?

[earloc]

Also, the above list could be extended to also support built-in types as:

• integrals

• floating-points

• bools

• chars

what about:

• Enums
• DateTimes
• DateTimeOffsets
• DateOnlys
• TimeOnlys