hostnet / entity-translation-bundle
Translation bundle to help with rendering pretty names for enum-like classes.
Installs: 87 368
Dependents: 0
Suggesters: 0
Security: 0
Stars: 5
Watchers: 6
Forks: 6
Open Issues: 1
Type:symfony-bundle
Requires
- php: ^8.1
- doctrine/annotations: ^1.3
- symfony/config: ^5.4|^6.0
- symfony/dependency-injection: ^5.4|^6.0
- symfony/framework-bundle: ^5.4|^6.0
- symfony/http-kernel: ^5.4|^6.0
- symfony/routing: ^5.4|^6.0
- symfony/translation: ^5.4|^6.0
- symfony/yaml: ^5.4|^6.0
Requires (Dev)
- hostnet/phpcs-tool: ^9.1.0
- phpunit/phpunit: ^9.5.6
- symfony/finder: ^5.4|^6.0
README
This bundle allows the automation of translating an enum value to a human readable string, for example, displaying a status text instead of the enum-value of a status code.
In it's essence, it allows to map a value to a translation within the domain that is the class name. What this means in practice is that you can use it as follows:
$status_text = $translator->trans(SetupStatus::DONE, [], SetupStatus::class);
Or in a twig template:
{{ constant('AppBundle\\Entity\\SetupStatus::DONE') | trans([], 'AppBundle\\Entity\\SetupStatus') }}
Requirements
The entity translation bundle requires at least php 7.3 and the symfony translation component. For specific requirements, please check composer.json
Installation
Installing is pretty straightforward, this package is available on packagist.
Example
$ composer require hostnet/entity-translation-bundle
Register The Bundle in your AppKernel
This bundle makes use of the translator which is registered by the framework bundle. So make sure you register this bundle after the FrameworkBundle
.
class AppKernel extends Kernel { public function registerBundles() { $bundles = [ // ... new AppBundle\AppBundle(), new Hostnet\Bundle\EntityTranslationBundle\HostnetEntityTranslationBundle(), // ... ]; return $bundles; } }
Usage
Simply add an enum.en.yml
to the translations folder in the Resources folder of one of your bundles. This will contain the translations for a given enum. The translation keys are the fully qualified namespaces in lowercase and an _
between CamelCase words. So for instance the enum AppBundle\Entity\SetupStatus
would become app_bundle.entity.setup_status
.
Consider the following class:
<?php namespace AppBundle\Entity; final class SetupStatus { const PENDING = 1; const DONE = 2; const ERROR = 3; const REVERTING_CHANGES = 4; }
Your AppBundle/Resources/translations/enum.en.yml
could look as followed:
app_bundle: entity: setup_status: pending : Installation Pending. done : Installation Complete. error : An error occured. reverting_changes : Reverting changes.
The translator will then pick up all enum classes defined in your translation file.