ditkrg/active_model_serializers
4
0
Fork 0
mirror of https://github.com/ditkrg/active_model_serializers.git synced 2026-01-23 06:16:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fixed typos

Browse Source
This commit is contained in:
Prathamesh Sonpatki 2013-03-26 17:36:26 +05:30
parent 049cff57c2
commit 7d1ce9c56e
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
DESIGN.textile
View File

@ -217,7 +217,7 @@ First, we specified the list of included attributes at the top of the class. Thi
NOTE: Internally, +ActiveModel::Serializer+ uses +read_attribute_for_serialization+, which defaults to +read_attribute+, which defaults to +send+. So if you're rolling your own models for use with the serializer, you can use simple Ruby accessors for your attributes if you like. NOTE: Internally, +ActiveModel::Serializer+ uses +read_attribute_for_serialization+, which defaults to +read_attribute+, which defaults to +send+. So if you're rolling your own models for use with the serializer, you can use simple Ruby accessors for your attributes if you like.
Next, we use the attributes methood in our +serializable_hash+ method, which allowed us to eliminate the +post+ method we hand-rolled Next, we use the attributes method in our +serializable_hash+ method, which allowed us to eliminate the +post+ method we hand-rolled
earlier. We could also eliminate the +as_json+ method, as +ActiveModel::Serializer+ provides a default +as_json+ method for earlier. We could also eliminate the +as_json+ method, as +ActiveModel::Serializer+ provides a default +as_json+ method for
us that calls our +serializable_hash+ method and inserts a root. But we can go a step further! us that calls our +serializable_hash+ method and inserts a root. But we can go a step further!
@ -354,7 +354,7 @@ h4. Modifying Associations
You can also rename associations if required. Say for example you have an association that You can also rename associations if required. Say for example you have an association that
makes sense to be named one thing in your code, but another when data is serialized. makes sense to be named one thing in your code, but another when data is serialized.
You can use the <code:key</code> option to specify a different name for an association. You can use the <code:key</code> option to specify a different name for an association.
Here is an exmaple: Here is an example:
<pre lang="ruby"> <pre lang="ruby">
class UserSerializer < ActiveModel::Serializer class UserSerializer < ActiveModel::Serializer

2
lib/active_model/array_serializer.rb
View File

@ -23,7 +23,7 @@ module ActiveModel
class_attribute :perform_caching class_attribute :perform_caching
class << self class << self
# set peform caching like root # set perform caching like root
def cached(value = true) def cached(value = true)
self.perform_caching = value self.perform_caching = value
end end