Releases: willdurand/BazingaJsTranslationBundle
Releases · willdurand/BazingaJsTranslationBundle
2.6.5 (2017-05-17)
2.6.4 (2017-02-13)
- Fix: translator.min.js had syntax errors when in strict mode (#196)
2.6.3 (2017-02-08)
2.6.2 (2016-12-16)
- Added: PHP 5.3 support (#182)
- Fix: Return default locale if none is found in the Javascript library (#183)
- Fix: Document public Translator.add API (#184)
- Added: Default count parameter in transchoice (#185)
- Fix: Use PhpUnit from composer when running the tests, to avoid collisions with PhpUnit PHAR file (#186)
2.6.1 (2016-09-20)
- Fix: Support for server side rendering using NodeJS (#179)
- Added:
npm run build
command insideResources/
to minify thetranslator.js
file.
2.6.0 (2016-09-01)
- Added: Support for
framework.translator.paths
configuration (more information in http://symfony.com/doc/2.8/translation.html) - Added:
--format
and--merge-domains
options tobazinga:js-translation:dump
command:--format
allows you to specify which formats must be included in the output--merge-domains
when set will generate only one file per locale with all the domains in it
- Removed: Kernel dependency from
TranslationFinder
. Every translation file is fetched from the Symfony's FrameworkBundle.
2.5.0 (2015-11-10)
- Added: Symfony3 support
2.4.0 (2015-10-27)
- Added: Widen
TranslationFinder::getLocations()
visibility to use is in an inheritant class - Added: update routing to expose
bazinga_jstranslation_js
- Added square brackets around optional arguments in doc blocks
- Fixed: create target dir if not exists
2.3.0 (2015-09-30)
- Added: support for Node.js
- Fixed: safer twig locale
- Fixed: Replace string casting on
ConfigCache
instance withgetPath()
to omit deprecated warning - Fixed: Replace
Validator
classname withValidation
to omit deprecated warning
2.2.2 (2015-06-01)
- Fixed: replaced routing deprecated arguments (#136)