Correct Text Domains in Translatable Strings#2061
Correct Text Domains in Translatable Strings#2061ravigadhiya007 wants to merge 1 commit intoWordPress:trunkfrom
Conversation
ravigadhiya007
requested review from
adamsilverstein,
felixarntz,
mukeshpanchal27,
pbearne and
westonruter
as code owners
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## trunk #2061 +/- ##
=======================================
Coverage 68.03% 68.03%
=======================================
Files 92 92
Lines 7631 7631
=======================================
Hits 5192 5192
Misses 2439 2439
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
The Make as closed. |
mukeshpanchal27
left a comment
mukeshpanchal27
left a comment
There was a problem hiding this comment.
Hi there, Thanks for the PR.
Check my comment #2061 (comment)
3 participants
Fixes #2060
Relevant technical choices
Updated the text domain in Performance Lab, Embed Optimizer, and Image Placeholders plugins to use the correct text domain based on each plugin’s slug.