-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use iOS localization handling for strings. #803
Conversation
Generated by 🚫 Danger Swift against 38d40f1 |
0139208
to
e02d356
Compare
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## develop #803 +/- ##
===========================================
- Coverage 52.07% 51.77% -0.31%
===========================================
Files 297 297
Lines 16544 16528 -16
Branches 9923 9914 -9
===========================================
- Hits 8616 8557 -59
- Misses 7678 7721 +43
Partials 250 250
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 3 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM just one question and one suggestion
e02d356
to
38d40f1
Compare
Kudos, SonarCloud Quality Gate passed!
|
Previously we had our own
calculatePreferredLanguages
method based uponLocale.preferredLanguages
to decide suitable languages for strings and then before translating we were doing additional work to manage locale regions if necessary.Turns out that
Bundle
has a method calledpreferredLocalizations
which does this for us and makes sure to only provide a single language (plus any regional variations) so you don't end up with the app showing strings in 3 or more languages.I've removed
Bundle.elementFallbackLanguage
in favour of thedevelopmentLocalization
property, but left in an override so that we can still run unit tests.There's a run of UI tests going on here, to make sure this works there too