i18n: Allow setting locale data by domain #5489
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #5168
Cherry-picks 685eaf0 from #5481
This pull request seeks to enable a plugin to inject their own domain locale data into the global
wp.i18n
module, refactoringgutenberg_get_jed_locale_data
as a general-purpose Jed locale formatter (removing previous assumptions of being the default domain).Example:
Testing instructions:
Verify that there are no regressions in the display of default localized strings for Gutenberg.
Try the example above in your browser console while on the Gutenberg screen, verifying that
"bar"
is logged to the console.