feat: added local translations for frontend-plugin-learner-dashboard #747
+42
−1
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.
Description
[Implemented Solution] I solved the plugin translation issue by creating a custom solution for the frontend-plugin-learner-dashboard component since its translations aren't available in the remote repository. I set up a dedicated local-overrides folder to store the manually translated Spanish content, then modified the Makefile's pull_translations command to automatically copy these local translations into the main messages directory whenever official translations are pulled. Finally, I updated the application's i18n configuration to always use these local plugin translations, ensuring that our custom Spanish translations persist and are never overwritten by future translation updates, while still allowing the rest of the application to receive official translation updates normally.
JIRA -> ENT-11106