aboutsummaryrefslogtreecommitdiffstats
path: root/activemodel/lib
Commit message (Collapse)AuthorAgeFilesLines
* remove stray (Vijay Dev2011-06-031-1/+1
|
* Change hashrocket spacing to match conventions.Ben Orenstein2011-06-021-2/+2
|
* Merge branch 'master' of git://github.com/lifo/docrailsXavier Noria2011-05-2513-24/+24
|\ | | | | | | | | | | Conflicts: actionmailer/lib/action_mailer/base.rb activesupport/lib/active_support/core_ext/kernel/requires.rb
| * Remove extra white spaces on ActiveModel docs.Sebastian Martinez2011-05-2313-24/+24
| |
* | Remove superfluous whitespace from ActiveModel::SecurePassword Daniel Schierbeck2011-05-221-1/+1
| | | | | | Only one space is needed, yo!
* | Bump versions for rc1David Heinemeier Hansson2011-05-211-1/+1
| |
* | ActionMailer deliver method Documentation corrected Ticket #761Ganesh Kumar2011-05-211-1/+1
| |
* | Specify the name to be used for ActiveModel::Name fixes #1168Yves Senn2011-05-201-2/+3
| | | | | | | | This patch allows to specify the name of your models independent of the class name.
* | Prefer each instead of for inGuillermo Iguaran2011-05-191-3/+1
|/
* Attributes with :string type should not be given the type passed in model ↵Jim Herzberg2011-05-181-1/+1
| | | | serialization options. Closes #1058
* Remove unneeded merge with default false optionsAkira Matsuda2011-05-161-4/+0
|
* Don't add DEFAULT_TOKENIZER to every instance of LengthValidator. Just use ↵Akira Matsuda2011-05-161-2/+2
| | | | it only when needed.
* Merge branch 'master' of git://github.com/lifo/docrailsXavier Noria2011-05-141-4/+4
|\ | | | | | | | | | | Conflicts: actionpack/lib/action_view/helpers/date_helper.rb railties/lib/rails/generators/rails/app/templates/config/initializers/wrap_parameters.rb.tt
| * Improve doc styles for ActiveModel::ConversionSebastian Martinez2011-05-041-4/+4
| |
* | Methods that return nil should not be considered YAMLJoshua Wehner2011-05-101-0/+1
| |
* | renamed mass-assignment scopes to roles, updated code, tests, docs and ↵Josh Kalderimis2011-05-081-23/+23
| | | | | | | | security guide
* | Add documentation for new observer enable/disable feature.Myron Marston2011-05-062-3/+51
| |
* | Prepare for beta1David Heinemeier Hansson2011-05-041-1/+1
|/
* Improved ActiveModel Observing docs.Sebastian Martinez2011-04-301-2/+4
|
* Merge branch 'master' of github.com:lifo/docrailsDan Pickett2011-04-293-4/+4
|\
| * Rephrased Dirty#changed? docsSebastian Martinez2011-04-261-1/+1
| |
| * Removed extra whitespaceSebastian Martinez2011-04-261-1/+1
| |
| * Better formatting on ActiveModel::TranslationSebastian Martinez2011-04-261-2/+2
| |
* | fix typoAditya Sanghi2011-04-291-1/+1
| |
* | :if should not fire on validations when not in context with :onAditya Sanghi2011-04-292-3/+3
| |
* | Fix bug with AM::Observer disablement.Myron Marston2011-04-282-25/+17
| | | | | | | | | | 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 :).
* | Fix dev env memory leaks by using AS::DescendantsTracker rather than keeping ↵Myron Marston2011-04-282-36/+12
| | | | | | | | | | track of subclasses manually. There's also no need to keep track of all ObserverArray instances in a hash, as this is likely to leak memory, too.
* | Revert "Revert "Handle enabling/disabling observers at different levels of ↵Myron Marston2011-04-282-3/+36
| | | | | | | | | | | | | | | | | | 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-282-36/+3
| | | | | | | | | | | | | | | | | | | | 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-282-3/+36
| | | | | | | | Last call wins.
* | Allow observers to be enabled and disabled.Myron Marston2011-04-282-3/+122
| | | | | | | | This is useful in situations like model unit tests and the occasional rake task to backfill old data.
* | Wrap line that is over 200 characters long. Now it's much easier to read.Myron Marston2011-04-281-1/+5
| |
* | minor correction to the AMo mass-assignment security docsJosh Kalderimis2011-04-241-1/+1
| |
* | AM mass assignment security attr_accessible and attr_protected now allow for ↵Josh Kalderimis2011-04-241-34/+85
|/ | | | | | | | scopes using :as => scope eg. attr_accessible :name attr_accessible :name, :admin, :as => :admin
* minor correction to the Active Model instantiate_observers docJosh Kalderimis2011-04-221-1/+1
|
* let this regexp be stricterXavier Noria2011-04-191-1/+1
| | | | | | | | | The purpose of this regexp is to detect strings that are valid identifiers to be used as method names. The anchor $ allows a trailing newline, and both ^ and $ may be bypassed because Ruby regexps are multiline always. The anchors \A and \z are the proper ones to ensure string boundaries.
* Let's not dup because value may not always be duplicable.José Valim2011-04-191-1/+1
|
* Avoid define_method if possible.José Valim2011-04-191-12/+39
|
* bcrypt will encrypt anything, so validate_presence_of would not catch nil / ↵Aaron Patterson2011-04-141-1/+3
| | | | blank passwords. Thank you to Aleksander Kamil Modzelewski for reporting this
* Declaring the attr_accessor for password_confirmation is not necessaryBrian Cardarella2011-04-141-2/+1
| | | | as the confirmation validation already adds that attr_accessor
* Remove `#among?` from Active SupportPrem Sichanugrist2011-04-131-1/+1
| | | | | | After a long list of discussion about the performance problem from using varargs and the reason that we can't find a great pair for it, it would be best to remove support for it for now. It will come back if we can find a good pair for it. For now, Bon Voyage, `#among?`.
* Merge branch 'master' of git://github.com/lifo/docrailsXavier Noria2011-04-121-1/+1
|\
| * RewordingOge Nnadi2011-04-111-1/+1
| |
* | Change Object#either? to Object#among? -- thanks to @jamesarosen for the ↵David Heinemeier Hansson2011-04-121-1/+1
| | | | | | | | suggestion!
* | Remove code duplication.José Valim2011-04-113-20/+27
| |
* | No need to rescue here. Invoking the wrong method in an object can happen ↵José Valim2011-04-113-6/+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-18/+14
| | | | | | | | | | | | | | | | `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-14/+18
| | | | | | | | | | | | 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-20/+76
|/ | | | | | ExclusionValidator, and FormatValidator You can now use a proc or lambda in :in option for InclusionValidator and ExclusionValidator, and :with, :without option for FormatValidator
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 08:26:29 +0000