Change LocalizedStringKey to LocalizedStringResource
Open
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 337
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
I'd recommend using the more modern localization type for UI. Since your minimum is macOS 13 you should be fine to migrate.
https://developer.apple.com/documentation/foundation/localizedstringresource
You're going to get more mileage.
Contributor guide
No contributing guide indexed for this repository
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 locating the UI uses of LocalizedStringKey and compare the migration requirements with Apple's LocalizedStringResource documentation. Done means the relevant localization types use LocalizedStringResource and the Mac and iPhone UI continues to localize correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- internationalization
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100