-
Notifications
You must be signed in to change notification settings - Fork 3
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
Missing text-domain for string translations #21
Comments
Hi @bahiirwa, good eye! The text domain hasn't been forgotten; these are actually the core texts, so, they don't require a text domain. :) |
On further consideration, I'm re-opening this issue. I see no harm in simply adding the text domain. It won't break anything and, well, it's only 3 strings. I'll get this into the 1.0.0 final release, which I anticipate in another week or so, just to be sure no further issues roll in. |
I think you should consider it. If you add text domain to "core" texts, they will not be translated. Never, because strings in UpdateClient.class.php for being translated need to have The line that adds the "View details" link, where there is |
Thanks, @xxsimoxx, for the additional information. Please open a dedicated issue for this part as it is different than the issue initially raised. I just don't want it to become lost in the mix. 😄 |
It seems I originally didn't comprehend what Simone was trying to say above. As he correctly points out, adding a text domain to the update client texts actually breaks the core translation functionality. In light of this, the text domain will be re-removed. For those who have trouble with builds or sniffs, just add your own text domain to the client file – the same domain that you're using in your plugin. |
Description
When I run the pre-hooks for building my plugin, I throws a warning for these lines in
classes/class-wc-update-client.php
specifically L182-184.Was this intentional to have
esc_html__
with a missing text domain?The text was updated successfully, but these errors were encountered: