-
-
Notifications
You must be signed in to change notification settings - Fork 5
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 string catalogues and fix non-localized strings #33
Conversation
@Supereg any idea why we are getting the |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #33 +/- ##
==========================================
- Coverage 76.42% 0.00% -76.41%
==========================================
Files 114 114
Lines 3952 3964 +12
==========================================
- Hits 3020 0 -3020
- Misses 932 3964 +3032
... and 94 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
Not sure why they pop up now. But feel free to add some |
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.
Thank you 🚀
Thanks. I added this and then I got a line length - sometimes you just can't win!! |
There is also a |
3e8ba56
to
bc94432
Compare
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.
@vishnuravi @Supereg Thank you for this fix!
Can we use this PR to directly resolve #22 which would have also been helpful to be done right in #32 to ensure that we don't run into the same issues again?
String catalogues should flag these issues and should automate these processes in the future 👍
c1d3184
to
6659604
Compare
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.
Thanks for the great work 🚀
As we migrated to String catalogues, we have some strings being picked up from the mock or preview implementations. I annotated every localization key I could find.
Would be great if you could review the usages of those keys and check if it makes sense to use the Text(verbatim:)
initializer instead, or, otherwise, add a translation for those strings.
Otherwise, the PR looks great, thanks for the effort 🎉
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.
Thank you @vishnuravi! Happy to get the PR merged once @Supereg is happy and his comments are resolved 🚀
Package.swift
Outdated
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.
Would be great if we can also just include the MD link check in there as well, just so we get it into the different repos as we make different smaller or bigger PRs 👍
@vishnuravi Following up on our discussion today: I addressed most of the issues with the localization files and only needed to translate a few very limited elements and added comments for the rest. Looking forward to getting the PR finished and feel free to merge it once all the conversations are resolved 👍 |
fyi, I'm currently rebasing this PR and taking care of it getting it merged if that is alright for you @vishnuravi 👍 |
ec6aa8f
to
487bb40
Compare
That sounds great, thank you @Supereg! |
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.
Thank you for finishing the PR @Supereg and thanks for all the work here @vishnuravi!
Use string catalogues and fix non-localized strings
⚙️ Release Notes
Migrates to use of string catalogues for localization and fixes a string that is not being drawn from the localization files.
📝 Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines: