- 16 5月, 2010 22 次提交
-
-
由 Simon Jefford 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Hussein Morsy 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 José Valim 提交于
-
由 pleax 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 rohit 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Aleksandr Koss 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 José Valim 提交于
-
由 Jeff Kreeftmeijer 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 José Valim 提交于
-
由 Jeff Kreeftmeijer 提交于
using :time_select when the attribute type is :time in the scaffold generator. [#2377 state:resolved] Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 rohit 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Elomar França 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 José Valim 提交于
-
由 José Valim 提交于
Ensure that eager_load actually takes place just after the middleware stack is built by using another pattern. Also create a engine_blank_point initializer to ensure any :before or :after hooks defined inside engines won't move the configuration initializers to other places.
-
由 Jeff Dean 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 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.
-
由 José Valim 提交于
-
由 Jeremy Kemper 提交于
-
由 Jeff Kreeftmeijer 提交于
Signed-off-by: NJeremy Kemper <jeremy@bitsweat.net>
-
由 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>
-
由 Santiago Pastorino 提交于
Signed-off-by: NPratik Naik <pratiknaik@gmail.com>
-
由 Jeff Kreeftmeijer 提交于
Signed-off-by: NJeremy Kemper <jeremy@bitsweat.net>
-
- 15 5月, 2010 18 次提交
-
-
由 Diego Algorta 提交于
Fix for get_ids when including a belongs_to association on a has_many association [#2896 state:resolved] Signed-off-by: NPratik Naik <pratiknaik@gmail.com>
-
由 Anil Wadghule 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Martin 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Paco Guzman 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 José Valim 提交于
-
由 wycats 提交于
Reorganized initializers a bit to enable better hooks for common cases without the need for Railtie. Specifically, the following hooks were added: * before_configuration: this hook is run immediately after the Application class comes into existence, but before the user has added any configuration. This is the appropriate place to set configuration for your plugin * before_initialize: This is run after all of the user's configuration has completed, but before any initializers have begun (in other words, it runs right after config/environments/{development,production,test}.rb) * after_initialize: This is run after all of the initializers have run. It is an appropriate place for forking in a preforking setup Each of these hooks may be used via ActiveSupport.on_load(name) { }. In all these cases, the context inside the block will be the Application object. This means that for simple cases, you can use these hooks without needing to create a Railtie.
-
由 wycats 提交于
-
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Carlos Antonio da Silva 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Neeraj Singh 提交于
[#4507 state:resolved] Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Adrian Sanchez 提交于
Bundler deprecated options in Gemfile with application template using method "gem" [#4534 state:resolved] Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Marc-Andre Lafortune 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Santiago Pastorino 提交于
[#4529 state:committed] Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 José Valim 提交于
-
由 Stephen Celis 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
and added AR::Base::clear_default_scope - clear_default_scope provides users who rely on the old behaviour of each call to default_scope overwriting any previous default scopes an opportunity to maintain that behaviour. [#4583 state:resolved] Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Neeraj Singh 提交于
[#4596 state:resolved] Signed-off-by: NJeremy Kemper <jeremy@bitsweat.net>
-
由 Santiago Pastorino 提交于
Signed-off-by: NJeremy Kemper <jeremy@bitsweat.net>
-