Support custom Locale
when using iOS 15 compatible String
initialiser
#52
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Unlike
LocalizedStringResource
, the properties within the generatedString.Localizable
type remain private to the generated source and cannot be directly accessed.This causes an issue if you need to be able to change the
Locale
value to something other than.current
.To address this, I've updated
String.init(localizable:)
to beString.init(localizable:locale:)
, with a nullable value.If the custom
locale
isnil
(the default value), we will use the original locale that is supplied by code generation.If a value is set, it will take priority and allows you to override the language returned, for example: