I18n – Automatic lookup of translations without translation_key

[Timmitry]

When building an Avo::BaseResource and defining fields, I need to specify the translation_key for each field individually, e.g.:

field :street, as: :text, translation_key: "activerecord.attributes.location.street"

This is tedious and feels unneccessary, especially since Rails is very good at doing this automatically (e.g. when building a form, I just use form.label :street, and it will infer the correct translation).

Would it be possible to add an automatic lookup of translation for attributes? Translations for attributes can be looked up with Location.human_attribute_name(:street). This will look in various places, for example attributes.street and activerecord.attributes.location.street.

It could be neccessary to specify the activerecord model that is described (Location in this example) in the avo resource for that.

[Paul-Bob]

This makes sense. I wonder if there are any use cases where this behavior is not desired.

Each field should check whether translation_key is provided and, if not, start a lookup. If there are cases where this behavior is not desired, we can make it configurable with a flag later and default it to true.