Releases: willdurand/BazingaJsTranslationBundle
1.2.1 - Compatibility Release
The package name has been renamed from willdurand/expose-translation-bundle
to willdurand/js-translation-bundle
. This release "replaces" the old package with the new one.
1.1.2 - Compatibility Release
The package name has been renamed from willdurand/expose-translation-bundle
to willdurand/js-translation-bundle
. This release "replaces" the old package with the new one.
1.0.3 - Compatibility Release
The package name has been renamed from willdurand/expose-translation-bundle
to willdurand/js-translation-bundle
. This release "replaces" the old package with the new one.
2.0.0-alpha3 - Third release before the upcoming major version!
- Changed: the
dump
command now generates files inweb/js/
by default (#84)
2.0.0-alpha2 - Second release before the upcoming major version!
- Fixed: preserve translation ids that are numeric values (#83)
2.0.0-alpha1 - Early release of the upcoming major version!
This bundle has been rewritten (75%), and it has led to a new major release. Nothing is backward compatible, and nothing has been done to ease compatibility between the two versions (1.x and 2.x). This bundle has been created three years ago, and it was time to refactor it. I am sorry for this BC break, sincerely.
This new version fixes a bunch of limitations, and potential bugs.
Upgrading from 1.x
to 2.x
is highly recommended. This requires a few changed (mostly naming changes) but also an update of your JavaScript code as the JS Translator
has changed too. Everything should is documented in this UPGRADE file.
Important: it is worth mentioning that it requires at least Symfony 2.3
and above.
Thank you,
William.
1.2.0
- Fixed: TranslationFinder to mimic FrameworkBundle's way to find translation files (#57)
- Fixed: JS dump not possible if i18n for route is enabled (#76)
- Updated: documentation, readme, etc. Update travis-ci config
- Changed: the bundle now requires Symfony 2.1 and above. While it looks like a BC break, I don't think the bundle worked well with Symfony 2.0 anyway, that is why I didn't bump the major version.
1.1.1
1.1.0
- Changed: visibility of
TranslationDumper::getTranslationMessages()
is nowprotected
.