- 16 2月, 2017 1 次提交
-
-
由 Sen Zhang 提交于
-
- 07 8月, 2016 1 次提交
-
-
由 Xavier Noria 提交于
-
- 27 6月, 2015 1 次提交
-
-
由 Radan Skoric 提交于
-
- 27 1月, 2014 1 次提交
-
-
由 Xavier Noria 提交于
Closes #11247.
-
- 13 1月, 2014 1 次提交
-
-
由 Yves Senn 提交于
-
- 28 5月, 2013 1 次提交
-
-
由 Charles Bergeron 提交于
Use Range#cover? for Numeric ranges (tests via endpoints) and use Range#include? for non-numeric ranges added changelog message
-
- 02 5月, 2013 1 次提交
-
-
由 Patrick Robertson 提交于
I also attempted to fix other styleguide violations such as { a: :b } over {a: :b} and foo(b: 'bar') over foo( b: 'bar' ).
-
- 26 10月, 2012 1 次提交
-
-
由 Francesco Rodriguez 提交于
-
- 21 10月, 2012 1 次提交
-
-
由 Francesco Rodriguez 提交于
-
- 25 8月, 2012 1 次提交
-
-
由 Gabriel Sobrinho 提交于
-
- 21 7月, 2012 2 次提交
-
-
由 Rafael Mendonça França 提交于
-
由 Rafael Mendonça França 提交于
-
- 10 7月, 2012 1 次提交
-
-
由 Bogdan Gusiev 提交于
-
- 06 7月, 2012 1 次提交
-
-
由 Francesco Rodriguez 提交于
-
- 05 7月, 2012 1 次提交
-
-
由 Francesco Rodriguez 提交于
-
- 26 6月, 2012 1 次提交
-
-
由 Francesco Rodriguez 提交于
-
- 12 6月, 2012 1 次提交
-
-
由 Akira Matsuda 提交于
-
- 16 5月, 2012 2 次提交
-
-
由 Francesco Rodriguez 提交于
-
由 Francesco Rodriguez 提交于
-
- 29 3月, 2012 1 次提交
-
-
由 Rafael Mendonça França 提交于
Orginal code by @jamescook Closes #1352 [Rafael Mendonça França + James Cook]
-
- 17 8月, 2011 1 次提交
-
-
由 Bogdan Gusiev 提交于
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
-
- 01 6月, 2011 1 次提交
-
-
由 Guillermo Iguaran 提交于
-
- 24 5月, 2011 1 次提交
-
-
由 Sebastian Martinez 提交于
-
- 12 4月, 2011 1 次提交
-
-
由 José Valim 提交于
-
- 11 4月, 2011 2 次提交
-
-
由 José Valim 提交于
No need to rescue here. Invoking the wrong method in an object can happen anywhere if you are not careful. In other words, test your shit.
-
由 José Valim 提交于
Revert "Add :use_include option to allow user to explicitly use `Range#include?` method in Ruby 1.9" Use :with => range.to_a instead. This reverts commit f6540211.
-
- 10 4月, 2011 2 次提交
-
-
由 Prem Sichanugrist 提交于
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.
-
由 Prem Sichanugrist 提交于
Add support for proc or lambda as an option for InclusionValidator, ExclusionValidator, and FormatValidator You can now use a proc or lambda in :in option for InclusionValidator and ExclusionValidator, and :with, :without option for FormatValidator
-
- 22 2月, 2011 1 次提交
-
-
由 Xavier Noria 提交于
-
- 21 2月, 2011 1 次提交
-
-
由 Xavier Noria 提交于
-
- 20 2月, 2011 2 次提交
-
-
由 Xavier Noria 提交于
-
由 Diego Carrion 提交于
[#6455 state:committed] Signed-off-by: NSantiago Pastorino <santiago@wyeworks.com>
-
- 19 2月, 2011 1 次提交
-
-
由 Frederick Cheung 提交于
Signed-off-by: NXavier Noria <fxn@hashref.com>
-
- 21 6月, 2010 2 次提交
-
-
由 José Valim 提交于
-
由 Jeroen van Dijk 提交于
Make ActiveModel::Errors#add_on_blank and #add_on_empty accept an options hash and make various Validators pass their (filtered) options. This makes it possible to pass additional options through Validators to message generation. E.g. plugin authors want to add validates_presence_of :foo, :format => "some format". Also, cleanup the :default vs :message options confusion in ActiveModel validation message generation. Also, deprecate ActiveModel::Errors#add_on_blank(attributes, custom_message) in favor of ActiveModel::Errors#add_on_blank(attributes, options). Also, refactoring of ActiveModel and ActiveRecord Validation tests. Test are a lot more DRY now. Better test coverage as well now. The first four points were reapplied from an older patch of Sven Fuchs which didn't apply cleanly anymore and was not complete yet. Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
- 16 6月, 2010 1 次提交
-
-
由 Rizwan Reza 提交于
-
- 16 5月, 2010 2 次提交
-
-
由 José Valim 提交于
Revert "Make ActiveModel::Errors#add_on_blank and #add_on_empty accept an options hash and make various Validators pass their (filtered) options." Having a huge array to whitelist options is not the proper way to handle this case. This means that the ActiveModel::Errors object should know about the options given in *all* validators and break the extensibility added by the validators itself. If the intent is to whitelist options before sending them to I18n, each validator should clean its respective options instead of throwing the responsibility to the Errors object. This reverts commit bc1c8d58.
-
由 Jeroen van Dijk 提交于
Make ActiveModel::Errors#add_on_blank and #add_on_empty accept an options hash and make various Validators pass their (filtered) options. This makes it possible to pass additional options through Validators to message generation. E.g. plugin authors want to add validates_presence_of :foo, :format => "some format". Also, cleanup the :default vs :message options confusion in ActiveModel validation message generation. Also, deprecate ActiveModel::Errors#add_on_blank(attributes, custom_message) in favor of ActiveModel::Errors#add_on_blank(attributes, options). Original patch by Sven Fuchs, some minor changes and has been changed to be applicable to master again [#4057 state:committed] Signed-off-by: NJeremy Kemper <jeremy@bitsweat.net>
-
- 14 5月, 2010 1 次提交
-
-
由 Josh Kalderimis 提交于
-
- 03 5月, 2010 1 次提交
-
-
由 Lawrence Pit 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-