This project is archived and is in readonly mode.
I18n ActiveModel Subclass Lookup
Reported by dwilkie | May 15th, 2010 @ 06:01 PM
Given the following Class definitions:
class Conversation class Message include ActiveModel::Validations attr_accessor :quantity validates :quantity, :presence => true end end
There is no way to reference the error messages for the Message class. For example the correct lookup for the class Conversation would be:
activemodel: errors: models: conversation: attributes: quantity: blank: "Some custom message"
But what is it for the Message class? I tried:
activemodel: errors: models: conversation: message: attributes: quantity: blank: "Some custom message" activemodel: errors: models: message: attributes: quantity: blank: "Some custom message" activemodel: errors: models: conversation::message: attributes: quantity: blank: "Some custom message"
None of them work.
If this is a bug then I would vote for the following to be the correct lookup:
activemodel: errors: models: conversation: message: attributes: quantity: blank: "Some custom message"
Comments and changes to this ticket
-
Rizwan Reza May 15th, 2010 @ 06:18 PM
- Tag changed from i18n to bugmash, i18n
-
pleax May 15th, 2010 @ 07:57 PM
This is not a bug. You can provide translation with following path:
LANG: activemodel: errors: models: conversation/message: attributes: quantity: blank: "Field is blank"
-
Jeroen van Dijk May 15th, 2010 @ 11:33 PM
It is not a bug, but I do think that the following is more appropriate though:
activemodel: errors: models: conversation: message: attributes: quantity: blank: "Some custom message"
This makes it dryer to have models under a specific namespace. Useful for engines too I think.
I can make a patch for it if others find this useful too.
-
Santiago Pastorino February 2nd, 2011 @ 04:38 PM
- State changed from new to open
- Importance changed from to Low
This issue has been automatically marked as stale because it has not been commented on for at least three months.
The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.
Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.
-
Santiago Pastorino February 2nd, 2011 @ 04:38 PM
- State changed from open to stale
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>