Skip to content
Commits on Nov 30, 2011
  1. @josevalim

    Revert "Implement ArraySerializer and move old serialization API to a…

    josevalim committed Nov 30, 2011
    … new namespace."
    
    This reverts commit 8896b4f.
    
    Conflicts:
    
    	activemodel/lib/active_model.rb
    	activemodel/lib/active_model/serializable.rb
    	activemodel/lib/active_model/serializer.rb
    	activemodel/test/cases/serializer_test.rb
Commits on Nov 23, 2011
  1. @josevalim

    Implement ArraySerializer and move old serialization API to a new nam…

    josevalim committed Nov 23, 2011
    …espace.
    
    The following constants were renamed:
    
      ActiveModel::Serialization     => ActiveModel::Serializable
      ActiveModel::Serializers::JSON => ActiveModel::Serializable::JSON
      ActiveModel::Serializers::Xml  => ActiveModel::Serializable::XML
    
    The main motivation for such a change is that `ActiveModel::Serializers::JSON`
    was not actually a serializer, but a module that when included allows the target to be serializable to JSON.
    
    With such changes, we were able to clean up the namespace to add true serializers as the ArraySerializer.
Commits on Sep 30, 2011
  1. @josevalim
Commits on Jun 26, 2010
  1. @josevalim

    Work around the fact the JSON gem was overwriting to_json implementat…

    josevalim committed Jun 26, 2010
    …ion for all Ruby core classes.
    
    This is required because the JSON gem is incompatible with Rails behavior and was not allowing ActiveModel::Errors to be serialized.
    So we need to ensure Rails implementation is the one triggered. [#4890 state:resolved]
Something went wrong with that request. Please try again.