Load translations from Translator's message catalogue #346
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.
Load translations from Translator's message catalogue
Context:
Existing implementation of BazingaJsTranslationBundle re-implements loading messages from files on disk. However, this implementation is not 1-to-1 compatible with message loading in Symfony's translator component. Thus some translations are not visible to BazingaJsTranslationBundle.
For example, LexikTranslationBundle stores messages in a DB,
This PR re-implements message discovery, such that it relies on
Symfony\Component\Translation\Translator
.This change was suggested in #277.
Backwards Compatibility: