8000 Upgrade information for the Translation component regarding the new L… · symfony/symfony@cd55a81 · GitHub
[go: up one dir, main page]

Skip to content

Commit cd55a81

Browse files
committed
Upgrade information for the Translation component regarding the new LoggingTranslator class.
1 parent 6a59db5 commit cd55a81

File tree

1 file changed

+40
-0
lines changed

1 file changed

+40
-0
lines changed

UPGRADE-2.6.md

Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -364,3 +364,43 @@ $bundles[] = new Symfony\Bundle\DebugBundle\DebugBundle();
364364
Then enjoy dumping variables by calling `dump($var)` anywhere in your PHP
365365
and `{% dump var %}` or `{{ dump(var) }}` in Twig. Dumps are displayed
366366
**in the web debug toolbar**.
367+
368+
Translation
369+
-----------
370+
371+
With `LoggingTranslator`, a new translator class is introduced with Symfony
372+
2.6. By default, the `@translator` service is referring to this class in the
373+
debug environment.
374+
375+
If you have own services that depend on the `@translator` service and expect
376+
this service to be an instance of either
377+
`Symfony\Component\Translation\Translator` or
378+
`Symfony\Bundle\FrameworkBundle\Translation\Translator`, e.g. by type-hinting
379+
for either of these classes, you will need to change that type hint. You can
380+
use the `TranslatorInterface` to be on the safe side for future changes.
381+
382+
Before:
383+
384+
```php
385+
use Symfony\Component\Translation\Translator;
386+
387+
class MyService {
388+
public function __construct(Translator $translator)
389+
{
390+
...
391+
}
392+
}
393+
```
394+
395+
After:
396+
397+
```php
398+
use Symfony\Component\Translation\TranslatorInterface;
399+
400+
class MyService {
401+
public function __construct(TranslatorInterface $translator)
402+
{
403+
...
404+
}
405+
}
406+
```

0 commit comments

Comments
 (0)
0