aboutsummaryrefslogtreecommitdiffstats
path: root/activemodel/lib/active_model/validations
Commit message (Collapse)AuthorAgeFilesLines
* fixing removed empty lines and examplesFrancesco Rodriguez2012-05-168-6/+11
|
* fixing validates_with docsFrancesco Rodriguez2012-05-161-6/+4
|
* better format and fixes to validators docsFrancesco Rodriguez2012-05-168-104/+154
|
* better example format in validates_exclusion_of docsFrancesco Rodriguez2012-05-161-2/+2
|
* Merge pull request #5942 from ↵Aaron Patterson2012-04-291-1/+2
|\ | | | | | | | | bcardarella/confirmation_error_message_on_confirmation_attribute confirmation validation error attribute
| * Support i18n attributes for confirmationBrian Cardarella2012-04-241-1/+2
| |
| * confirmation validation error attributeBrian Cardarella2012-04-231-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | This will render the error message on :#{attribute}_confirmation instead of on attribute itself. When rendering confirmation errors inline on the form with form builders such as SimpleForm and Formtastic it is confusing to the ender user to see the confirmation error message on the attribute element. Instead it makes more sense to have this validation error render on the confirmation field instead. The i18n message has been updated for the confirmation validator error message to include the original attribute name.
* | minor docs improvementsOscar Del Ben2012-04-261-3/+3
|/
* fix ActiveModel::Validations::Callbacks docJan Xie2012-04-151-1/+2
|
* Remove code duplication in InclusionValidator and ExclusionValidator.Rafael Mendonça França2012-03-283-44/+39
| | | | | | | | Orginal code by @jamescook Closes #1352 [Rafael Mendonça França + James Cook]
* Prefer || over 'or' for boolean operationsBenjamin Quorning2012-02-221-1/+1
|
* remove unnecessary require core_ext/string/encodingSergey Nartimov2012-02-141-2/+0
|
* To infinity… and beyond!Niels Ganser2012-02-061-2/+2
| | | | | | | Allow infinite values for validates_length_of. Particularly useful for prettily defining an open ended range such as validates_length_of :human_stupidity, :within => 0..Float::INFINITY
* AS::Callbacks: :skip_after_callbacks_if_terminated optionBogdan Gusiev2012-02-031-2/+1
|
* revise docs [ci skip]Vijay Dev2012-02-011-3/+3
|
* Generate strict validation error messages with attribute nameCarlos Antonio da Silva2012-02-011-7/+6
|
* whitespacesdreamfall2012-01-171-3/+3
|
* validates method should not change options argumentdreamfall2012-01-171-1/+1
|
* Merge branch 'master' of github.com:lifo/docrailsVijay Dev2012-01-111-1/+1
|\
| * Update ConfirmationValidator docs, correct when the validator runsAlan Harper2012-01-051-1/+1
| |
* | Remove Array.wrap call in ActiveModelRafael Mendonça França2012-01-061-2/+2
|/
* don't call an extra method if options[:tokenizer] is not presentVasiliy Ermolovich2011-12-241-4/+2
|
* use Range#min and Range#max to reduce extra statementVasiliy Ermolovich2011-12-241-2/+1
|
* deprecate String#encoding_aware? and remove its usageSergey Nartimov2011-12-241-2/+0
|
* added :other_than => :!= option to numericality validatorJakub Kuźma2011-12-211-2/+3
|
* Ensure length validator also works on 1.8.7.José Valim2011-12-061-6/+17
|
* Don't tokenize string when counting charactersIan Young2011-12-041-2/+1
|
* Fix argument error message for length validationAlexey Vakhov2011-12-011-1/+1
|
* Cosmetic fixes in AM validatations docsAlexey Vakhov2011-11-272-4/+4
|
* Fix a tiny typo in custom validators documentationJean Boussier2011-11-101-1/+1
|
* Use .add instead of << to add errorsEvgeniy Dolzhenko2011-10-112-3/+3
|
* Typo fixBogdan Gusiev2011-08-251-1/+1
|
* Implemented strict validation conceptBogdan Gusiev2011-08-1710-5/+35
| | | | | | | 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
* Fix example code for #validates_with instance methodBen Marini2011-07-241-2/+2
|
* Merge branch 'master' of git://github.com/lifo/docrailsXavier Noria2011-06-061-3/+3
|\ | | | | | | | | Conflicts: activerecord/RUNNING_UNIT_TESTS
| * remove stray (Vijay Dev2011-06-031-1/+1
| |
| * Change hashrocket spacing to match conventions.Ben Orenstein2011-06-021-2/+2
| |
* | Don't add .rb in requiresGuillermo Iguaran2011-05-312-2/+2
|/
* Remove extra white spaces on ActiveModel docs.Sebastian Martinez2011-05-237-13/+13
|
* 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.
* fix typoAditya Sanghi2011-04-291-1/+1
|
* :if should not fire on validations when not in context with :onAditya Sanghi2011-04-291-2/+2
|
* 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.
* 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
* Refactor length validationSantiago Pastorino2011-03-121-3/+3
|
* length validation for fixnumsAndriy Tyurnikov2011-03-121-1/+2
| | | | Signed-off-by: Santiago Pastorino <santiago@wyeworks.com>