Skip to content

[Feature] - Make exception message translation consistent #28

@smaillet

Description

@smaillet

Is your feature request related to a problem? Please describe.
Currently, the exception reporting sometimes uses a hard coded 'en-us' string while others use a translatable string. These should all use the same for for consistency. Also, for consistency with the core runtime and BCLs, the strings should be translated resources.

Describe the solution you'd like
All exception message now, and in the future, should use exception messages.

Describe alternatives you've considered
Leave it random, and likely hard coded (Usually, simpler, but a refactoring tool could help here). This is not consistent with how the runtime and BCL works and thus has a limited form of the exceptions

Additional context
There has been MUCH debate on whether exception messages should be translated or not. For WinRT they are usually not translated. However, for .NET the existing runtime, BCL, Compiler and tooling ALL do use translated resources. So it is likely best to follow that. ("When in Rome...")

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions