Closed shadinaif closed 1 year ago
Thanks for the pull request, @shadinaif! Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket as you can:
All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
Please let us know once your PR is ready for our review and all tests are green.
Resolved the conversation with an errant click, unresolved and ran that tests.
Patch and project coverage have no change.
Comparison is base (
f9dac31
) 97.68% compared to head (e4bb599
) 97.68%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
Hi @MichaelRoytman! Would you mind taking a look at this? Thanks!
Hi, @mphilbrick211! I took a look a few weeks ago and left a few questions for Shadi. If they could address my remaining questions, I'd be happy to re-review. I want to confirm the impact on Javascript string translations and on existing translations in the repository. Thank you.
Hi, @mphilbrick211! I took a look a few weeks ago and left a few questions for Shadi. If they could address my remaining questions, I'd be happy to re-review. I want to confirm the impact on Javascript string translations and on existing translations in the repository. Thank you.
Hi, @mphilbrick211! I took a look a few weeks ago and left a few questions for Shadi. If they could address my remaining questions, I'd be happy to re-review. I want to confirm the impact on Javascript string translations and on existing translations in the repository. Thank you.
Hi, @mphilbrick211! I took a look a few weeks ago and left a few questions for Shadi. If they could address my remaining questions, I'd be happy to re-review. I want to confirm the impact on Javascript string translations and on existing translations in the repository. Thank you.
Oof. Github is having issues and posted my comment four times. Sorry for tagging you four times! 😅
Hi, @mphilbrick211! I took a look a few weeks ago and left a few questions for Shadi. If they could address my remaining questions, I'd be happy to re-review. I want to confirm the impact on Javascript string translations and on existing translations in the repository. Thank you.
Hi @shadinaif! Friendly ping on this :)
Hi @MichaelRoytman and @mphilbrick211 , thank you for your patience on this. I'll push an update and address the issues above very soon. We decided to finish the project without introducing any breaking changes until the last phase of it. I'll add a detailed description to the PR, we're working on a template for that
Thank you!
@MichaelRoytman please review now, tested on devstack olive, works fine. We're not changing any behavior in this phase, please see the details in the PR description. Thank you!
@shadinaif Looks like there are some test failures.
Thank you @e0d . The error is related to a missing token for codecov.io . It's either deleted by someone, or affected by latest Github incident and needs to be re-set https://github.blog/2023-03-23-we-updated-our-rsa-ssh-host-key/
Merging PR on behalf of Shadi, as it has 3 approvals and looks good to me.
@shadinaif 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future.
feat: standardize translation directory for i18n_tool
This PR prepares the repository to comply with openedx-translations by doing the following:
Move all local translations to
conf/locale
and converttranslations
into a symbolic link toconf/locale
. The reason behind that is to comply with openedx-translations mechanism that requires translation files to be inconf/locale
directory. This fix will avoid the need to modifyfind
commands herelocale
link is removed as it is not needed anymoreMake the translation command
make extract_translations
build a file nameddjango.po
instead oftext.po
. And create a symbolic link fromtext.po
todjango.po
. This is because openedx-translations requiresdjango.po
as the name of the file. And it must be a valid file (not a link) because it usesgit add
here[x] Tested on local devstack palm to ensure that everything renders fine
[x] Tested on local devstack palm to ensure that local translation still works
References
This pull request is part of the FC-0012 project which is sparked by the Translation Infrastructure update OEP-58.
Check the links above for full information about the overall project.
Internalization is being rearchitected in Open edX Python, XBlock, Micro-frontend, and other projects. There are a number of immediately visible changes:
.json
,.po
or.mo
files will be committed into the repos.make extract_translations
in all repositoriesBreaking Changes
One of the primary goals of the project is to avoid breaking changes. If you noticed any suspicious code, please raise your concern. But before that, please know the strategy we're following to avoid breaking changes
For XBlocks:
conf/locale
. Therefore, we are creating a link fromconf/locale
totranslations
so Atlas can find the path without disrupting the current way of having translations locally within the XBlocks