You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, in Translatable, the created table contains an object_class column that stores the specific class name.
I propose allowing custom strings (opt-in) instead of specific class names, similar to how Doctrine allows user-defined strings for its inheritance map.
For example, a App\Entity\Skill class is normally mapped to its FQCN, but it could be overridden with a "skill" string.
The reason for this request is that modifying the class FQCN (e.g., moving the namespace or renaming the class) requires running a database migration to remap all translations. Ideally, this change would allow code modification without necessitating a database update.
The text was updated successfully, but these errors were encountered:
Feature Request
Currently, in Translatable, the created table contains an
object_class
column that stores the specific class name.I propose allowing custom strings (opt-in) instead of specific class names, similar to how Doctrine allows user-defined strings for its inheritance map.
For example, a
App\Entity\Skill
class is normally mapped to its FQCN, but it could be overridden with a"skill"
string.The reason for this request is that modifying the class FQCN (e.g., moving the namespace or renaming the class) requires running a database migration to remap all translations. Ideally, this change would allow code modification without necessitating a database update.
The text was updated successfully, but these errors were encountered: