-
Notifications
You must be signed in to change notification settings - Fork 119
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
Generate tutorial addons #3638
Generate tutorial addons #3638
Conversation
Codecov Report
@@ Coverage Diff @@
## main #3638 +/- ##
==========================================
- Coverage 61.86% 61.00% -0.86%
==========================================
Files 270 277 +7
Lines 17812 18104 +292
Branches 8907 8981 +74
==========================================
+ Hits 11019 11044 +25
- Misses 5107 5337 +230
- Partials 1686 1723 +37
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
610d823
to
591856d
Compare
We also need to define the behavior between main and branches. We need to support branches, in case an add-on gets removed. Do we merge the ts if there is already a file with the same name? That seems like the most sensible approach. |
Not 100% sure it works or how the resulting XLIFF looks like, but this is the idea Also, other Python clean-ups: https://github.com/flodolo/mozilla-vpn-client/commit/fc135e4df450bce75e5c1b2af6745b9f5246a4eb BTW, how are you going to import back translations? There's nothing in the current PR. |
Co-authored-by: Francesco Lodolo <[email protected]>
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.
Overall, I think this is pretty good and aside from a few minor changes I don't see any major problems with merging this work. We should still have enough time for these changes to settle before the fix and code freeze deadlines.
Note: as mentioned before, this is still missing the "import strings" part. But I'd be OK with keeping that as a separate follow-up, when you actually have the strings in the repo to use. |
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.
Looks good!
No description provided.