You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 12, 2024. It is now read-only.
Is your feature request related to a problem? Please describe.
I'm submitting this issue to shed light on the need for a reference regarding the string resources utilized within the app for localization and text display purposes. Currently, there's a lack of a concise reference for these essential string resources.
Describe the solution you'd like
I'd like to see a reference guide that provides a comprehensive list of all string resources used within the app. This guide should include explanations or contexts for each string resource, clarifying their intended usage and purpose within the app.
Describe alternatives you've considered
One alternative could be creating inline comments within the codebase that explain the purpose and context of each string resource.
Additional context
There might be scenarios where new team members join the project or when developers, translators, or localization teams need clarity on the context and usage of various string resources. Having a comprehensive documentation or reference for these strings would streamline development, localization efforts, and overall maintenance of the app.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I'm submitting this issue to shed light on the need for a reference regarding the string resources utilized within the app for localization and text display purposes. Currently, there's a lack of a concise reference for these essential string resources.
Describe the solution you'd like
I'd like to see a reference guide that provides a comprehensive list of all string resources used within the app. This guide should include explanations or contexts for each string resource, clarifying their intended usage and purpose within the app.
Describe alternatives you've considered
One alternative could be creating inline comments within the codebase that explain the purpose and context of each string resource.
Additional context
There might be scenarios where new team members join the project or when developers, translators, or localization teams need clarity on the context and usage of various string resources. Having a comprehensive documentation or reference for these strings would streamline development, localization efforts, and overall maintenance of the app.
The text was updated successfully, but these errors were encountered: