Fix RailsModelMatcher to recognize slash notation in ActiveRecord attribute translations

[wagner]

Fixes #702

Problem

The RailsModelMatcher incorrectly reported missing translations when using Model.human_attribute_name with dot notation that should resolve to slash notation in locale files.

Rails' human_attribute_name method has special logic that converts dot notation to slash notation when looking up nested attribute translations. This is commonly used for STI (Single Table Inheritance) models and enum-like nested attributes.

Example

Locale file (config/locales/en.yml):

en:
  activerecord:
    attributes:
      product/status:
        active: Active
        inactive: Inactive

View code:

<%= Product.human_attribute_name("status.active") %>
# => "Active"

Before this fix:

• i18n-tasks looked for: activerecord.attributes.product.status.active
• Incorrectly reported as missing

After this fix:

• i18n-tasks correctly looks for: activerecord.attributes.product/status.active
• No false positives

Solution

Updated both the AST-based (RailsModelMatcher) and Prism-based scanners to detect when an attribute name contains a dot and convert the separator between the model name and attribute to a slash, matching Rails' internal behavior.

Changes

• lib/i18n/tasks/scanners/ast_matchers/rails_model_matcher.rb: Added logic to use slash separator when attribute contains a dot
• lib/i18n/tasks/scanners/prism_scanners/visitor.rb: Applied the same conversion logic for the Prism scanner
• Test coverage: Added comprehensive tests for both Ruby and ERB files to ensure the slash notation is correctly recognized

Testing

• ✅ All existing tests pass (257 examples, 0 failures)
• ✅ Added new test cases for slash notation pattern
• ✅ Tested with both AST and Prism-based scanners
• ✅ Verified backward compatibility: regular attributes without dots continue to work as before

Test Cases Added

1. Ruby files: Product.human_attribute_name("status.active")
2. ERB files: <%= Product.human_attribute_name("status.active") %>
3. Both scanners (AST and Prism) recognize the pattern correctly

Backward Compatibility

This change is fully backward compatible. Attributes without dots continue to use the standard dot notation:

• Archive.human_attribute_name(:name) → activerecord.attributes.archive.name ✅

References

• Rails i18n Guide - Translations for Active Record Models
• Issue RailsModelMatcher doesn't recognize slash notation in ActiveRecord attribute translations #702

[davidwessman]

Nice 🙂 Thank you for fixing this 🙂

Please fix the rubocop errors, then I wonder if we need to skip the candidate key for the human_attribute_name if we have the dot-notation. Can you double check the behaviour in a Rails app?.

[wagner]

Lots of changes here because I had to split the tests: Spec/ExampleLength: Example has too many lines. [158/140]

[wagner]

The reorganization made it hard to see, but here's the only actual change in the test. 👆

[davidwessman]

Nice 🙂 thank you!