I’m not sure it’s guaranteed what order these validations get run in, as it might depend on how the attributes hash itself ends up ordered. You may be better off making your validate method more resilient and simply not run if some of the required data is missing. For example: def within_required_range? return if ([ … Read more
Rails 4 now has features from the strong_parameters gem built in by default. One no longer has to make calls :as => :admin, nor do you need the attr_accessible :user_attribute, :as => admin in your model. The reason for this is that, by default, rails apps now have ‘security’ for every attribute on models. You … Read more
I am not a huge fan of the other approach because it ties the test too close to the implementation. Also, it’s fairly hard to follow. This is the approach I ultimately use. Please keep in mind that this is a gross oversimplification of what my validator actually did… just wanted to demonstrate it more … Read more
You can have multiple serializers for the same model, e.g. class SimplePersonSerializer < ActiveModel::Serializer attributes :id, :name end and class CompletePersonSerializer < ActiveModel::Serializer attributes :id, :name, :phone, :email end simple info for people in one controller: render json: @people, each_serializer: SimplePersonSerializer complete info for people in another: render json: @people, each_serializer: CompletePersonSerializer simple info for … Read more
You don’t need a plugin for basic needs. You can do this to get a hash of all validators. ModelName.validators If you want to get the validators for a specific field : ModelName.validators_on(:attribute)
You probably have a query that doesn’t return all the columns (i.e. uses :select) and then cache_money; or some other ActiveRecord plugin uses an after_initialize callback, which executes whenever a new ActiveRecord object is created (i.e. when fetched from the database). In that initialize callback, something tries to access or use an attribute that wasn’t … Read more
By convention in rails (and this is enforced by autoloader), file paths should match namespaces. So, if you have a Mailboxer::Message model, it should be in app/models/mailboxer/message.rb. Additionally, you probably have autoloader kicking in when trying to load a Message class (my guess is that it happens from within ActAsMessageable). It looks for a message.rb … Read more
Rails 3 is designed with modularity in mind. Each module has its own purpose and functionality. ActiveModel: This component was created in Rails 3. They took all the model related parts that did not have a database requirement of Rails 2 ActiveRecord and moved it into ActiveModel. So ActiveModel includes things like validations. More information: … Read more
In Rails 3, for your model “Driver”, you want Driver.columns_hash. Driver.columns_hash[“name”].type #returns :string If you want to iterate through them, you’d do something like this: Driver.columns_hash.each {|k,v| puts “#{k} => #{v.type}”} which will output the following: id => integer name => string created_at => datetime updated_at => datetime
I was looking to use this for an after_save callback. A simpler solution is to use id_changed? (since it won’t change on update) or even created_at_changed? if timestamp columns are present. Update: As @mitsy points out, if this check is needed outside of callbacks then use id_previously_changed?. See docs.