Commit message (Collapse) | Author | Age | Files | Lines | ||
---|---|---|---|---|---|---|
... | ||||||
* | | | Rename new method to_path to to_partial_path to avoid conflicts with ↵ | José Valim | 2011-08-01 | 2 | -7/+7 | |
| |/ |/| | | | | | File#to_path and similar. | |||||
* | | Merge pull request #2034 from Casecommons/to_path | José Valim | 2011-07-28 | 2 | -5/+20 | |
|\ \ | | | | | | | Allow ActiveModel-compatible instances to define their own partial paths | |||||
| * | | Let ActiveModel instances define partial paths. | Grant Hutchins & Peter Jaros | 2011-07-25 | 2 | -5/+20 | |
| |/ | | | | | | | | | | | Deprecate ActiveModel::Name#partial_path. Now you should call #to_path directly on ActiveModel instances. | |||||
* / | Handle the empty array correctly. | thedarkone | 2011-07-27 | 1 | -0/+1 | |
|/ | ||||||
* | ActiveModel support for the :include serialization option | John Firebaugh | 2011-07-17 | 2 | -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 test | John Firebaugh | 2011-07-17 | 1 | -0/+5 | |
| | ||||||
* | serializable_hash(:only => [], :methods => [:foo]) should work | John Firebaugh | 2011-07-17 | 1 | -0/+10 | |
| | ||||||
* | Enable passing root: false to #to_json | Joe Fiorini | 2011-07-01 | 1 | -1/+52 | |
| | ||||||
* | changing an attribute multiple times retains the correct original value | Ian Stewart | 2011-06-28 | 1 | -0/+9 | |
| | ||||||
* | Allow to specify mass-assignment roles as array | Alexander Uvarov | 2011-06-23 | 1 | -0/+14 | |
| | ||||||
* | Merge pull request #1654 from ganeshkumar/test_cases | Santiago Pastorino | 2011-06-13 | 1 | -1/+0 | |
|\ | | | | | removed duplicate code in tests | |||||
| * | removed duplicate code | ganesh | 2011-06-11 | 1 | -1/+0 | |
| | | ||||||
* | | Get rid of the alternate namespace lookup. | José Valim | 2011-06-11 | 1 | -10/+0 | |
|/ | ||||||
* | Brought back alternative convention for namespaced models in i18n. | thoefer | 2011-06-08 | 1 | -0/+10 | |
| | ||||||
* | Transform the symbol into a constant lookup. | José Valim | 2011-05-31 | 1 | -4/+4 | |
| | ||||||
* | ActiveModel::MassAssignmentSecurity.mass_assignment_sanitizer method | Bogdan Gusiev | 2011-05-30 | 1 | -5/+13 | |
| | | | | | In order to specify your own sanitize method Implemented .mass_assignment_sanitizer configuration option | |||||
* | MassAssignmentSecurity: add ability to specify your own sanitizer | Bogdan Gusiev | 2011-05-26 | 4 | -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 Agrawal | 2011-05-22 | 1 | -1/+0 | |
| | ||||||
* | Specify the name to be used for ActiveModel::Name fixes #1168 | Yves Senn | 2011-05-20 | 1 | -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 Herzberg | 2011-05-18 | 1 | -1/+7 | |
| | | | | serialization options. Closes #1058 | |||||
* | Follow code conventions on some tests | Sebastian Martinez | 2011-05-10 | 4 | -29/+29 | |
| | ||||||
* | Methods that return nil should not be considered YAML | Joshua Wehner | 2011-05-10 | 1 | -0/+4 | |
| | ||||||
* | renamed mass-assignment scopes to roles, updated code, tests, docs and ↵ | Josh Kalderimis | 2011-05-08 | 1 | -2/+2 | |
| | | | | security guide | |||||
* | :if should not fire on validations when not in context with :on | Aditya Sanghi | 2011-04-29 | 1 | -0/+14 | |
| | ||||||
* | Add additional tests for AM::ObserverArray that I had missed yesterday. | Myron Marston | 2011-04-28 | 1 | -1/+50 | |
| | ||||||
* | Fix bug with AM::Observer disablement. | Myron Marston | 2011-04-28 | 1 | -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 Marston | 2011-04-28 | 1 | -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é Valim | 2011-04-28 | 1 | -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 Marston | 2011-04-28 | 1 | -0/+39 | |
| | | | | Last call wins. | |||||
* | Allow observers to be enabled and disabled. | Myron Marston | 2011-04-28 | 2 | -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 Kalderimis | 2011-04-24 | 2 | -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 Patterson | 2011-04-14 | 1 | -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é Valim | 2011-04-11 | 3 | -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é Valim | 2011-04-11 | 2 | -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 places | Prem Sichanugrist | 2011-04-11 | 1 | -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 Sichanugrist | 2011-04-10 | 2 | -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 Sichanugrist | 2011-04-10 | 3 | -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 directory | John Firebaugh | 2011-04-06 | 2 | -0/+0 | |
| | | | | Hopefully "serializeration" is not an in joke that I missed. | |||||
* | Do not in place modify what table_name returns | Santiago Pastorino | 2011-03-22 | 1 | -11/+0 | |
| | ||||||
* | define_attr_method should be able to define methods that returns nil | Santiago Pastorino | 2011-03-17 | 1 | -0/+2 | |
| | ||||||
* | dup strings on return so that in place modifications do not break anything. ↵ | Aaron Patterson | 2011-03-17 | 1 | -0/+11 | |
| | | | | I am looking at you "compute_table_name" | |||||
* | define_attr_method correctly defines methods with invalid identifiers | Santiago Pastorino | 2011-03-16 | 1 | -2/+4 | |
| | ||||||
* | Add a define_attr_method test | Santiago Pastorino | 2011-03-16 | 1 | -0/+13 | |
| | ||||||
* | Add test for define_attr_method using as name an invalid identifier | Santiago Pastorino | 2011-03-16 | 1 | -0/+13 | |
| | ||||||
* | Add test for define_attribute_method using as name an invalid identifier | Santiago Pastorino | 2011-03-16 | 1 | -3/+26 | |
| | ||||||
* | Refactor length validation | Santiago Pastorino | 2011-03-12 | 1 | -3/+3 | |
| | ||||||
* | length validation for fixnums | Andriy Tyurnikov | 2011-03-12 | 1 | -0/+11 | |
| | | | | Signed-off-by: Santiago Pastorino <santiago@wyeworks.com> | |||||
* | Active Model typos. | R.T. Lechow | 2011-03-05 | 1 | -1/+1 | |
| | ||||||
* | Move ActiveModel::AttributeMethods#attribute_methods_generated? to ↵ | Alexander Uvarov | 2011-03-01 | 1 | -3/+7 | |
| | | | | | | | | ActiveRecord, so it's flexible now [#6428 state:resolved] Signed-off-by: José Valim <jose.valim@gmail.com> | |||||
* | Revert "Properly interpolate i18n keys in modules [#5572 state:resolved]" | Santiago Pastorino | 2011-02-27 | 1 | -19/+0 | |
| | | | | | | | This breaks #6448, you should use :"module/class" as key for namespacing [#6448 state:committed] This reverts commit 8d30193b08bd2321a7a78a1f481bd5e4d4d45557. |