aboutsummaryrefslogtreecommitdiffstats
path: root/activemodel/test/cases/mass_assignment_security
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* 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-263-25/+5
| | | | | | Added an ability to specify your own behavior on mass assingment protection, controlled by option: ActiveModel::MassAssignmentSecurity.mass_assignment_sanitizer
* 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?.
* Avoid interpreted as grouped expression warningsSantiago Pastorino2010-07-111-1/+1
|
* mass_assignment_security moved from AR to AMo, and minor test cleanupJosh Kalderimis2010-07-084-0/+123
Signed-off-by: José Valim <jose.valim@gmail.com>