Improve declaration of translatable fields in a model #714
enzedonline
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Relating to when you want to exclude a field from being translatable.
Currently, it requries creating a translatable_fields attribute then listing all the fields you want to be translatble.
This is kind of a pain as it is really the reverse of what you'd most commonly want to do, to exclude a field. On a model with 25 fields where I want to exclude one field, I have to make a
translatable_fieldswith 24 fields listed and keep that maintained in case of model changes.It also requires looking in two places for field definition and translation definition.
I'd prefer to define this in the field definition with a translatable attribute, set to
Falseon those fields to be excluded. Easier reading, less maintennance.Similar case with
synchronized.All reactions