You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This translations by default do not work, they only ever use the default in the translation object where ever used.
With prefixPluginTranslations as a util used in registerTrads the correct data structure is output - translation files can be properly read. Either a change is needed to the getTranslations output or the addition of the original prefixPluginTranslations is needed.
Steps to reproduce the behavior
Generate a plugin
Try use a translation
Add the prefixPluginTranslations util in registerTrads
See correct output for plugin translations
Expected behavior
I think this helper function is needed by default or an update is needed in getTranslations, something like this?
Bug report
Required System information
Describe the bug
When generating a plugin, by default registerTrads uses 'getTranslations' for data, which results in:
This translations by default do not work, they only ever use the default in the translation object where ever used.
With prefixPluginTranslations as a util used in registerTrads the correct data structure is output - translation files can be properly read. Either a change is needed to the getTranslations output or the addition of the original prefixPluginTranslations is needed.
Steps to reproduce the behavior
Expected behavior
I think this helper function is needed by default or an update is needed in getTranslations, something like this?
Code snippets
The console without prefix util:
The console with prefix:
The text was updated successfully, but these errors were encountered: