aboutsummaryrefslogtreecommitdiffstats
path: root/activemodel/test/cases
Commit message (Collapse)AuthorAgeFilesLines
...
* | add has_key? to ActiveModel::ErrorsDamien Mathieu2011-09-061-0/+6
| |
* | Merge pull request #2563 from bogdan/internal_validationJosé Valim2011-08-251-0/+33
|\ \ | | | | | | Implemented strict validation concept
| * | Implemented strict validation conceptBogdan Gusiev2011-08-171-0/+33
| | | | | | | | | | | | | | | | | | | | | 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
* | | added more tests for only-include and except-include options in serializationAnand2011-08-231-1/+14
|/ /
* | Allow ActiveRecord observers to be disabled.Myron Marston2011-08-121-0/+12
| | | | | | We have to use Observer#update rather than Observer#send since the enabled state is checked in #update before forwarding the method call on.
* | Merge pull request #2385 from bogdan/test_default_sanitizer2José Valim2011-08-011-1/+9
|\ \ | | | | | | MassAssignmentProtection: consider 'id' insensetive in StrictSanitizer
| * | MassAssignmentProtection: consider 'id' insensetive in StrictSanitizerBogdan Gusiev2011-07-281-1/+9
| | | | | | | | | | | | | | | | | | In order to use StrictSanitizer in test mode Consider :id as not sensetive attribute that can be filtered from mass assignement without exception.
* | | Rename new method to_path to to_partial_path to avoid conflicts with ↵José Valim2011-08-012-7/+7
| |/ |/| | | | | File#to_path and similar.
* | Merge pull request #2034 from Casecommons/to_pathJosé Valim2011-07-282-5/+20
|\ \ | | | | | | Allow ActiveModel-compatible instances to define their own partial paths
| * | Let ActiveModel instances define partial paths.Grant Hutchins & Peter Jaros2011-07-252-5/+20
| |/ | | | | | | | | | | Deprecate ActiveModel::Name#partial_path. Now you should call #to_path directly on ActiveModel instances.
* / Handle the empty array correctly.thedarkone2011-07-271-0/+1
|/
* ActiveModel support for the :include serialization optionJohn Firebaugh2011-07-172-8/+117
| | | | | | | | | | | | | | | | | | | | 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.
* Add a testJohn Firebaugh2011-07-171-0/+5
|
* serializable_hash(:only => [], :methods => [:foo]) should workJohn Firebaugh2011-07-171-0/+10
|
* Enable passing root: false to #to_jsonJoe Fiorini2011-07-011-1/+52
|
* changing an attribute multiple times retains the correct original valueIan Stewart2011-06-281-0/+9
|
* Allow to specify mass-assignment roles as arrayAlexander Uvarov2011-06-231-0/+14
|
* Merge pull request #1654 from ganeshkumar/test_casesSantiago Pastorino2011-06-131-1/+0
|\ | | | | removed duplicate code in tests
| * removed duplicate codeganesh2011-06-111-1/+0
| |
* | Get rid of the alternate namespace lookup.José Valim2011-06-111-10/+0
|/
* Brought back alternative convention for namespaced models in i18n.thoefer2011-06-081-0/+10
|
* Transform the symbol into a constant lookup.José Valim2011-05-311-4/+4
|
* ActiveModel::MassAssignmentSecurity.mass_assignment_sanitizer methodBogdan Gusiev2011-05-301-5/+13
| | | | | In order to specify your own sanitize method Implemented .mass_assignment_sanitizer configuration option
* MassAssignmentSecurity: add ability to specify your own sanitizerBogdan Gusiev2011-05-264-25/+25
| | | | | | Added an ability to specify your own behavior on mass assingment protection, controlled by option: ActiveModel::MassAssignmentSecurity.mass_assignment_sanitizer
* No more need rubygems here.Arun Agrawal2011-05-221-1/+0
|
* Specify the name to be used for ActiveModel::Name fixes #1168Yves Senn2011-05-201-1/+38
| | | | This patch allows to specify the name of your models independent of the class name.
* Attributes with :string type should not be given the type passed in model ↵Jim Herzberg2011-05-181-1/+7
| | | | serialization options. Closes #1058
* Follow code conventions on some testsSebastian Martinez2011-05-104-29/+29
|
* Methods that return nil should not be considered YAMLJoshua Wehner2011-05-101-0/+4
|
* renamed mass-assignment scopes to roles, updated code, tests, docs and ↵Josh Kalderimis2011-05-081-2/+2
| | | | security guide
* :if should not fire on validations when not in context with :onAditya Sanghi2011-04-291-0/+14
|
* Add additional tests for AM::ObserverArray that I had missed yesterday.Myron Marston2011-04-281-1/+50
|
* Fix bug with AM::Observer disablement.Myron Marston2011-04-281-0/+10
| | | | | 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 :).
* Revert "Revert "Handle enabling/disabling observers at different levels of ↵Myron Marston2011-04-281-0/+39
| | | | | | | | | 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.
* Revert "Handle enabling/disabling observers at different levels of the class ↵José Valim2011-04-281-39/+0
| | | | | | | | | | 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.
* Handle enabling/disabling observers at different levels of the class hierarchy.Myron Marston2011-04-281-0/+39
| | | | Last call wins.
* Allow observers to be enabled and disabled.Myron Marston2011-04-282-0/+127
| | | | This is useful in situations like model unit tests and the occasional rake task to backfill old data.
* AM mass assignment security attr_accessible and attr_protected now allow for ↵Josh Kalderimis2011-04-242-11/+39
| | | | | | | | scopes using :as => scope eg. attr_accessible :name attr_accessible :name, :admin, :as => :admin
* bcrypt will encrypt anything, so validate_presence_of would not catch nil / ↵Aaron Patterson2011-04-141-0/+12
| | | | blank passwords. Thank you to Aleksander Kamil Modzelewski for reporting this
* No need to rescue here. Invoking the wrong method in an object can happen ↵José Valim2011-04-113-34/+0
| | | | anywhere if you are not careful. In other words, test your shit.
* Revert "Add :use_include option to allow user to explicitly use ↵José Valim2011-04-112-19/+0
| | | | | | | | `Range#include?` method in Ruby 1.9" Use :with => range.to_a instead. This reverts commit f6540211b5b9133c9f93c11655a04d613c237e67.
* Using Object#in? and Object#either? in various placesPrem Sichanugrist2011-04-111-1/+2
| | | | 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?.
* Add :use_include option to allow user to explicitly use `Range#include?` ↵Prem Sichanugrist2011-04-102-0/+19
| | | | | | 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.
* Add support for proc or lambda as an option for InclusionValidator, ↵Prem Sichanugrist2011-04-103-0/+82
| | | | | | ExclusionValidator, and FormatValidator You can now use a proc or lambda in :in option for InclusionValidator and ExclusionValidator, and :with, :without option for FormatValidator
* Rename test directory to match code directoryJohn Firebaugh2011-04-062-0/+0
| | | | Hopefully "serializeration" is not an in joke that I missed.
* Do not in place modify what table_name returnsSantiago Pastorino2011-03-221-11/+0
|
* define_attr_method should be able to define methods that returns nilSantiago Pastorino2011-03-171-0/+2
|
* dup strings on return so that in place modifications do not break anything. ↵Aaron Patterson2011-03-171-0/+11
| | | | I am looking at you "compute_table_name"
* define_attr_method correctly defines methods with invalid identifiersSantiago Pastorino2011-03-161-2/+4
|
* Add a define_attr_method testSantiago Pastorino2011-03-161-0/+13
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-10-30 06:12:31 +0000