diff options
| author | John Firebaugh <john_firebaugh@us.ibm.com> | 2011-02-21 22:55:49 -0800 |
|---|---|---|
| committer | John Firebaugh <john_firebaugh@us.ibm.com> | 2011-07-17 11:34:07 -0700 |
| commit | 4860143ee4ccafef474f14f40b8f70c2b6b54656 (patch) | |
| tree | 1fa5a120a4b1d6f79feaf4b7dc18c3c41de6e523 /activeresource | |
| parent | 1723a7a6c6098eaa61ce964bebca2ed5f8f947b7 (diff) | |
| download | rails-4860143ee4ccafef474f14f40b8f70c2b6b54656.tar.gz rails-4860143ee4ccafef474f14f40b8f70c2b6b54656.tar.bz2 rails-4860143ee4ccafef474f14f40b8f70c2b6b54656.zip | |
ActiveModel support for the :include serialization option
This commit moves support for the :include serialization option for
serializing associated objects out of ActiveRecord in into ActiveModel.
The following methods support the :include option:
* serializable_hash
* to_json
* to_xml
Instances must respond to methods named by the values of the :includes
array (or keys of the :includes hash). If an association method returns
an object that is_a?(Enumerable) (which AR has_many associations do), it
is assumed to be a collection association, and its elements must respond
to :serializable_hash. Otherwise it must respond to :serializable_hash
itself.
While here, fix #858, XmlSerializer should not singularize already
singular association names.
Diffstat (limited to 'activeresource')
0 files changed, 0 insertions, 0 deletions