Add test case for interpolation with passing of data along with record #24431
Conversation
…d attribute in error message, where a proc is passed.
|
@rafaelfranca @prathamesh-sonpatki #24119 is kind of a breaking change, before that we returned "activemodel.errors.models.topic.attributes.title.blank" as first key in this example (as documented here- #22427 it's newly documented though), and now we return object. |
|
That's true. Because here - https://github.com/svenfuchs/i18n/blob/aee7b3f6072fba3f54798a280bd6007536b039cd/lib/i18n/backend/base.rb#L120-L121 We check for presence of object in options first and if not we pass the key (activemodel.errors.models.topic.attributes.title.blank) passed from Rails to the proc. After #24119, the options[:object] will always be not null so key won't be passed to proc. Can a key be used in the proc with proper usecase? The example in #22427 didn't use it. |
|
Urgh. Lets change the example added in #22427 to match this new API and add a CHANGELOG entry about it. |
|
Ok. Will take care of it. |
…records [ci skip] - This change is made as the behavior for `:message` proc was changed in rails#24119. - Also check rails#24431 (comment) for reference.
Follow-up of #24119
r? @rafaelfranca