| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previously, it would use send() to get the attribute. In Active
Resource, this would rely on hitting method missing. If a method with
the same name was defined further up the ancestor chain, that method
would wrongly be called.
This change fixes test_to_xml_with_private_method_name_as_attribute in
activeresource/test/cases/base_test.rb, which was broken after
51bef9d8fb0b4da7a104425ab8545e9331387743, because that change made
to_xml use serializable_hash.
|
| | | |
|
| | |
| | |
| | |
| | | |
include the root, but an instance is serialized with the root option passed as true
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There's no harm in generating a method name that's already defined on
the host class, since we're generating the attribute methods in a module
that gets included. In fact, this is desirable as it allows the host
class to call super.
|
| | |
| | |
| | |
| | | |
This can be overloaded by implementors if necessary.
|
| | |
| | |
| | |
| | |
| | | |
If super was false earlier, it is still going to be false, so we don't
need to call it again at the end of the method.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Check respond_to_without_attributes? in method_missing. If there is any
method that responds (even private), let super handle it and raise
NoMethodError if necessary.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This means that attribute methods which don't exist will get generated
when define_attribute_methods is called, so we don't have to use hacks
like `attribute_method_suffix ''`.
|
|/ / |
|
| | |
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | | |
method, not attribute.
|
|/ / |
|
|\ \
| | |
| | | |
Implemented strict validation concept
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In order to deliver debug information to dev team
instead of display error message to end user
Implemented strict validation concept
that suppose to define validation that always raise exception when fails
|
|/ / |
|
|\ \ |
|
| | |
| | |
| | |
| | | |
while porting to the rails repo)
|
|\| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
RELEASING_RAILS.rdoc
actionpack/lib/sprockets/railtie.rb
actionpack/test/template/sprockets_helper_test.rb
activerecord/test/cases/calculations_test.rb
railties/guides/source/3_1_release_notes.textile
railties/guides/source/active_resource_basics.textile
railties/guides/source/command_line.textile
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
In order to use StrictSanitizer in test mode
Consider :id as not sensetive attribute that can be filtered from
mass assignement without exception.
|
| | |
| | |
| | |
| | | |
File#to_path and similar.
|
| | |
| | |
| | |
| | | |
internal method.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Deprecate ActiveModel::Name#partial_path. Now you
should call #to_path directly on ActiveModel
instances.
|
| | | |
|
| | |
| | |
| | | |
We have to use Observer#update rather than Observer#send since the enabled state is checked in #update before forwarding the method call on.
|
|\ \ \
| | | |
| | | | |
MassAssignmentProtection: consider 'id' insensetive in StrictSanitizer
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In order to use StrictSanitizer in test mode
Consider :id as not sensetive attribute that can be filtered from
mass assignement without exception.
|
| | | |
| | | |
| | | |
| | | | |
File#to_path and similar.
|
| | | |
| | | |
| | | |
| | | | |
internal method.
|
|\ \ \ \
| | | | |
| | | | | |
Allow ActiveModel-compatible instances to define their own partial paths
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | | |
Deprecate ActiveModel::Name#partial_path. Now you
should call #to_path directly on ActiveModel
instances.
|
|\ \ \ \
| |_|/ /
|/| | | |
Improve AM::Errors#include?
|
| |/ / |
|
|/ / |
|
|\ \ |
|
| | |
| | |
| | |
| | | |
ActiveModel::Dirty.
|
|\ \ \
| | | |
| | | | |
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.
|
| | | | |
|
| |/ / |
|
| | | |
|
| | | |
|
|/ / |
|
| | |
|