Skip to content

Conversation

shouichi
Copy link
Contributor

@shouichi shouichi commented Aug 2, 2024

Problem:

f6c0a35 changed human_attribute_name to raise error if raise_on_missing_translations is true. This change had a major impact on existing applications (i.e., too many missing translation errors).

Solution:

Change human_attribute_name to raise an error iff raise_on_missing_translations is :strict.

Copy link
Member

@byroot byroot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, it's mosty a question of how much we want to "advertise" this.

@ghiculescu any opinions?

@ghiculescu
Copy link
Member

This looks good to me. I agree with not changing the defaults in the template files.

Problem:

f6c0a35 changed `human_attribute_name`
to raise error if `raise_on_missing_translations` is `true`. This change
had a major impact on existing applications (i.e., too many missing
translation errors).

Solution:

Change `human_attribute_name` to raise an error iff
`raise_on_missing_translations` is `:strict`.
@shouichi shouichi force-pushed the raise-on-missing-translations-strict branch from 40549eb to 8b511de Compare August 2, 2024 23:16
@shouichi shouichi requested review from MatheusRich and byroot August 2, 2024 23:17
@jhawthorn jhawthorn merged commit 9d241e6 into rails:main Aug 9, 2024
3 checks passed
@jhawthorn
Copy link
Member

Thank you!

@shouichi shouichi deleted the raise-on-missing-translations-strict branch August 9, 2024 23:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants