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
Adds missing keys from i18n tasks output #11958
Adds missing keys from i18n tasks output #11958
Conversation
e357ce1
to
e408f3e
Compare
ad2b09b
to
4ec0085
Compare
0c8b0f5
to
88dbcdb
Compare
8a1489e
to
88dbcdb
Compare
e032490
to
d1fb704
Compare
missing_keys.txt
Outdated
@@ -47,7 +47,7 @@ | |||
| all | spree.remove | app/views/spree/admin/taxons/_taxon_table.html.haml:15 | - missing translation, added key -> not sure though, where to trigger this missing translation | |||
| all | spree.shipment_mailer.base_subject.picked_up_subject | app/mailers/spree/shipment_mailer.rb:15 | - exists in en.yml, seems to be a false positive | |||
| all | spree.taxon_edit | app/views/spree/admin/taxons/edit.html.haml:4 | - missing translation, added key | |||
| all | thank_you_for_your_order | app/views/spree/orders/show.html.haml:26 | | |||
| all | thank_you_for_your_order | app/views/spree/orders/show.html.haml:26 | - missing translation, added key | |||
| all | unrecognized_card_type | app/views/spree/admin/payments/source_forms/_gateway.html.haml:25 | |
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.
Another option could have been to reuse the key thanks: "Thank you for your business."
.
config/locales/en.yml
Outdated
unrecognized_card_type: "" | ||
use_new_cc: "Use a new credit card" | ||
what_is_this: "What is this?" | ||
your_cart_is_empty: "Your cart is empty" |
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.
I'm not sure these keys are needed... But they are indeed missing.
d1fb704
to
e284d11
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.
Great pull request! Easy to follow, step by step.
And nice cleanup along the way. 😍
741420f
to
278e56c
Compare
I've noticed there were these two files (which I've marked as needing issues to fix missing translations):
However, after a second look, I'm convinced they are not in use, so I've removed them still within this PR. Re-requesting review 🙏 |
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.
Nice one ! Thanks for that 🙏 , it seems like an unpleasant task.
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.
I'm convinced they are not in use, so I've removed them still within this PR.
Thank you! I forgot to remove them in a712f25.
@filipefurtad0 will this PR close #2626 ? |
Hey @RachL , I'd say the actual PR contributing to #2626 is #11906, as per this comment. I'm not sure we should keep it open though as we've improved the previous code to detect more types of missing translations, and because we've opted not to implement any of the follow-up suggestions (references, comment above and here) like:
So, I'd say yes, let's close! |
I've checked staging, and I could not find this message, nor the entry in the en.yml file - I think we're not rendering this message currently, hence, the removal.
I'm not sure how to trigger this error, and triggering an update error message seems appropriate too - it's sort of an edge case, perhaps this is a valid approach
Adds string to missing key To be squashed
Done to prevent/fix merge conflicts
Deletes file We only needed this file for tracking progress, during review, we should not keep it in master I think
_learn and _connect seem to appear at the top of the homepage (and not as pane). Also, there was some hard coded URLs which seems not to be used, as the translations in the Configuration/Content section seem to work correctly.
278e56c
to
d2c2e20
Compare
Hi @drummer83 , thanks for testing this one! There are cases in which indeed, I don't know how to trigger the respective behavior. Some of them looked like dead code, so I've removed them in this PR. In other cases, I had no basis to assume that, and I felt it is better to add a key, then being to thorough on the grooming, which could actually create missing translations... Adding a key should not have any negative impact on the functionality of the app; worst case scenario, it's adding a key which is never rendered in the frontend. I don't see this as a big risk, so I've added keys on points
On 4:
Good point. I guess this was my initial intention but left the key there, hanging. Done here. Thanks for spotting it!
None, the PR should not affect the pages. However, some files were removed, which could affect the page, but are not supposed to. This is the commit.
Nice catch! Done on the latest commit bfd4b73. I think I've addressed everything. There are two new minor commits so I'm moving to code review. Thanks again @drummer83 🙏 |
Thanks, @filipefurtad0, for clarifying and updating the last bits! I have tested the changes of your latest commits. |
@filipefurtad0 Can you please confirm if this PR contained user-facing changes or not? I quickly scanned and couldn't see any evidence, but could be wrong. |
Hey @dacook, |
Sorry I missed that, yes that sounds good 👍 |
What? Why?
Related to #11938.
The output from
i18n-tasks missing
has been added to this PR - it will be deleted on the last commit once all the entries have been verified. The idea is to check all of them and either ignore (if the key is found on en.yml - this seems to happen for dynamic keys) or add it toen.yml
it it is indeed verified to be missing. In some case, the view file has been deleted, this is the case for:What should we test?
The scope is missing translations, so ideally, a quick test in using en.yml and a second locale should be done for the following pages, which should render well:
/admin/stripe_connect_settings/edit
-> Instance Publishable Keyverify that translations work as before on all pages, during customer checkout
I've removed this file, I don't think it is used:
As superadmin, check taxonomy pages, namely editing and creating new taxonomies. Can you find a remove button? Is it rendering correctly?
As a customer, initiate the checkout process, by adding some items to the cart. Edit the cart. Is the
Continue shopping
button displayed correctly, as before?As admin, edit an order without any payments. Are you able to see any message stating that "the order has no payments"? I believe this was never the case. In summary: going through the side tabs, when editing an order as admin, should display all information correctly.
Ideally, we would trigger the flash message: "The order could not be updated" but I don't know how to trigger this. Will ask testers and update instructions.
As superadmin, editing states pages should display correctly
As superadmin, under
/admin/contents/edit
, verify that it is possible to enable/disable theMenu 6 icon name
andMenu 7 icon name
sections of the homepage.Release notes
Changelog Category (reviewers may add a label for the release notes):
The title of the pull request will be included in the release notes.
Dependencies
Documentation updates