TeamAmaze / TeamAmaze/AmazeFileManager
Proper naming convention of i18n string keys
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe.
Code healthiness, better maintenance of the string table for internationalization/translation work
Describe the solution you'd like
We shall rename the string keys to a standardized convention, e.g. <domain>.<subdomain>.<component>.<category>.<type>
Such as
app.sftp.SftpConnectDialog.ui.connectionName.label
app.sftp.SftpConnectDialog.message.connect.ssh_host_key_verification.title
app.sftp.SftpConnectDialog.message.connect.ssh_host_key_verification.prompt
instead of reinventing a naming scheme on almost every new PR that would update strings.xml.
Describe alternatives you've considered
N/A
Additional context
N/A
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing strings.xml resources and their current key patterns. Compare them with the proposed domain/subdomain/component/category/type convention and determine the scope of any required renaming; done would mean an agreed, consistently applied naming scheme across the string table.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- internationalization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100