# \[ANN\] ClassyInheritance 0.4.0

**URL:** <https://www.ruby-forum.com/t/ann-classyinheritance-0-4-0/141208>\
**Category:** Rails\
**Created:** [June 23, 2008, 5:00pm UTC](https://www.ruby-forum.com/t/ann-classyinheritance-0-4-0/141208 "2008-06-23T17:00:30Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![starmaerker](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/e9bcb4/32.png) [@starmaerker](https://www.ruby-forum.com/u/starmaerker)\
**Post date:** [June 23, 2008, 5:00pm UTC](https://www.ruby-forum.com/t/ann-classyinheritance-0-4-0/141208/1 "2008-06-23T17:00:30Z")

</div>

_About:_

[http://stonean.com/wiki/classy-inheritance](http://stonean.com/wiki/classy-inheritance)

Classy Inheritance simplifies the definition and implementation of one  
object depending on another object. For example, a User object  
depending on  
a Person object. If you do the following:

class User \< ActiveRecord::Base

depends\_on :person, :attrs =\> [:first\_name, :last\_name, :email]

end

You will get @user.first\_name, @user.last\_name and @user.email  
functionality. So, direct usage of these attributes can be used on your  
form and the Person associated is created/maintained for you. e.g.:

\<% text\_field :user, :first\_name %\>

_In this release_:

Classy Inheritance now adds support for the standard Rails association  
options.

If your depends\_on call includes the :as attribute (polymorphic  
associations), the Rails association used is _:has\_one_, otherwise it’s  
\*  
:belongs\_to\*.

So, you can now add options such as :dependent and :class\_name.

_As there are multiple option combination choices, I haven’t tested them  
all. So, please let me know if you run into an issue._

There is a wiki, forum and issue tracking for Classy Inheritance at  
[http://stonean.com](http://stonean.com)

## thanks, andy

Andrew S.