pagerduty / active-record-ex

A library to make ActiveRecord::Relations even more awesome

Deprecated

This library is no longer in active development.

ActiveRecordEx

A library to make ActiveRecord::Relations even more awesome.

ActiveRecordEx is made of several modules that are used by includeing them on your ActiveRecord model classes.

Installation

Run

gem install active-record-ex

or add

gem 'active-record-ex', '~> 0.2.1'

to your Gemfile.

Compatibility

Currently, only ActiveRecord 3.2 is supported. However, other versions have not been tested and may be compatible.

Modules

AssocOrdering

Extends setters for has_many associations so that ordering of association arrays is persisted.

AssumeDestroy

Changes the behavior of accepts_nested_attributes_for so that an explicit _destroy: true is not required to destroy an association model.

Instead, all models in the association will be destroyed if they are not included in the set of models used to update the association.

ManyToMany

Allows chaining of calls to has_many and belongs_to relationships.

NillableFind

Allows you to treat passing nil to a parent association as representing the "parent" of all of the child associations without a parent association.

PolymorphicBuild

Allows choosing the subclass of a model in an association via a passed :type parameter, useful for accepts_nested_attributes_for on a polymorphic association.

Development

Run tests with rake test.

active-record-ex's Issues

Rename to "EmbracesNestedAttributes" and remove ManyToMany/NillableFind

ManyToMany's already made available in https://github.com/PagerDuty/manytomany and is thematically different from the other modules present here. NillableFind isn't there, but perhaps should be.

The other ones are about making passing nested attributes through #update_attributes, #create, #build_attributes, et al more flexible, while ManyToMany and NillableFind are simply about making building complicated queries easier. These are very different things, and should be kept separate to reflect that.

The naming of "EmbracesNestedAttributes" (Or perhaps "LovesNestedAttributes") would better capture the purpose of the modules that would remain.

ManyToMany should support non string class name

Seeing this error when attempting to create a many to many relationship:

NoMethodError: undefined method constantize' for #Class:0x007feae9c62f60`

It was solved when making the class_name in the association definition a string.