| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
| | |
| | |
| | | |
This can be overloaded by implementors if necessary.
|
| | |
| | |
| | |
| | |
| | |
| | | |
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 ''`.
|
| | | |
|
| |/
|/| |
|
| | |
|
|\ \
| | |
| | | |
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
|
|/ / |
|
| |
| |
| | |
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.
|
|\ \
| | |
| | | |
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.
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
removed duplicate code in tests
|
| | |
|
|/ |
|
| |
|
| |
|
|
|
|
|
| |
In order to specify your own sanitize method
Implemented .mass_assignment_sanitizer configuration option
|
|
|
|
|
|
| |
Added an ability to specify your own behavior on mass assingment
protection, controlled by option:
ActiveModel::MassAssignmentSecurity.mass_assignment_sanitizer
|
| |
|
|
|
|
| |
This patch allows to specify the name of your models independent of the class name.
|
|
|
|
| |
serialization options. Closes #1058
|
| |
|
| |
|
|
|
|
| |
security guide
|
| |
|
| |
|
|
|
|
|
| |
Now that we propagate the enabling/disabling to descendants, we no longer have to check the disabled_observer Set on each superclass of the model class. This was causing a bug when disabling all observers at a superclass level and then enabling an individual observer at a subclass level.
Plus the logic is simpler now :).
|
|
|
|
|
|
|
|
|
| |
the class hierarchy.""
This reverts commit 2a25c5818b03d7d6cd63aad180bff23479dbd861.
I'm going to add another commit that keeps the same behavior of fixes
the problems of leaking memory in development.
|
|
|
|
|
|
|
|
|
|
| |
hierarchy."
This reverts commit ad62f1928768bd2676958a4a08512bad342fe469 because the current
subclasses implementation leaks memory in development.
Instead of keeping an array of subclasses, the better solution is to
ask the parent if an observer is being disabled or not.
|
|
|
|
| |
Last call wins.
|
|
|
|
| |
This is useful in situations like model unit tests and the occasional rake task to backfill old data.
|
|
|
|
|
|
|
|
| |
scopes using :as => scope eg.
attr_accessible :name
attr_accessible :name, :admin, :as => :admin
|
|
|
|
| |
blank passwords. Thank you to Aleksander Kamil Modzelewski for reporting this
|
|
|
|
| |
anywhere if you are not careful. In other words, test your shit.
|
|
|
|
|
|
|
|
| |
`Range#include?` method in Ruby 1.9"
Use :with => range.to_a instead.
This reverts commit f6540211b5b9133c9f93c11655a04d613c237e67.
|
|
|
|
| |
There're a lot of places in Rails source code which make a lot of sense to switching to Object#in? or Object#either? instead of using [].include?.
|
|
|
|
|
|
| |
method in Ruby 1.9
In Ruby 1.9 we're currently use `Range#cover?` to fix the performance problem. However, there might be the case that you want to use `Range#include?` instead. This patch will give you that option.
|
|
|
|
|
|
| |
ExclusionValidator, and FormatValidator
You can now use a proc or lambda in :in option for InclusionValidator and ExclusionValidator, and :with, :without option for FormatValidator
|