Skip to content

Standardize string resource namingΒ #181

Description

@amarradi

String resource names in strings.xml should follow a consistent naming convention to improve maintainability, translation workflow, and overall code readability.

βœ… Suggested naming convention:

πŸ”  Examples:

menu_about
title_edit_note
msg_unsaved_changes

btn_save
hint_note_title
dialog_delete_confirmation

πŸ“Œ Naming guidelines:

Use lowercase letters and underscores

Avoid camelCase, spaces, or special characters

Structure names by purpose:

title_ β†’ screen titles
btn_ β†’ button text
menu_ β†’ menu items
msg_ β†’ user-facing messages
hint_ β†’ input hints
dialog_ β†’ dialog titles or messages

Optional: Prefix with screen/module name (e.g., editnote_btn_save)

Metadata

Metadata

Assignees

No one assigned

    Labels

    nice to haveIt would be nice if this were implemented

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions