fix: translation_key
class attribute
#3565
Merged
+20
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes #3538
The
translation_key
method defined in the base resource relied on an instance attribute,@translation_key
, which was alwaysnil
.Previously, a bug in Rails (prior to this Rails PR) inadvertently redefined the class attribute reader for all sub-classes that defined the class attribute, causing
translation_key
to exhibit the expected behavior by chance. After the fix in Rails 8.0.1, the correct reader from the parent class is now used. However, since@translation_key
is an instance attribute rather than a class-level attribute, it remainsnil
, and the method defaults to the fallback value. Check rails/rails#53992 for more details.To fix this, I renamed the class attribute to
custom_translation_key
and aliased the writer totranslation_key
for backward compatibility.Checklist: