- 30 6月, 2013 2 次提交
-
-
由 Neeraj Singh 提交于
Method `delete_all` should not be invoking callbacks and this feature was deprecated in Rails 4.0. This is being removed. `delete_all` will continue to honor the `:dependent` option. However if `:dependent` value is `:destroy` then the default deletion strategy for that collection will be applied. User can also force a deletion strategy by passing parameter to `delete_all`. For example you can do `@post.comments.delete_all(:nullify)`
-
由 Santiago Pastorino 提交于
-
- 29 6月, 2013 13 次提交
-
-
由 Rafael Mendonça França 提交于
Fix `rails plugin --help`
-
由 schneems 提交于
Right now if you run the `rails plugin --help` command it fails because rails expects a command in `railties/lib/rails/commands/plugin.rb` that does not exist because the file is named `plugin_new`. This is the error: ``` ruby-2.0.0-p0 ~/documents/projects/tmp/vanilla (master) $ rails plugin --help /Users/schneems/.rvm/gems/ruby-2.0.0-p0/gems/activesupport-4.0.0/lib/active_support/dependencies.rb:228:in `require': cannot load such file -- rails/commands/plugin (LoadError) from /Users/schneems/.rvm/gems/ruby-2.0.0-p0/gems/activesupport-4.0.0/lib/active_support/dependencies.rb:228:in `block in require' from /Users/schneems/.rvm/gems/ruby-2.0.0-p0/gems/activesupport-4.0.0/lib/active_support/dependencies.rb:213:in `load_dependency' from /Users/schneems/.rvm/gems/ruby-2.0.0-p0/gems/activesupport-4.0.0/lib/active_support/dependencies.rb:228:in `require' from /Users/schneems/.rvm/gems/ruby-2.0.0-p0/gems/railties-4.0.0/lib/rails/commands.rb:49:in `<top (required)>' from bin/rails:4:in `require' from bin/rails:4:in `<main>' ```
-
由 José Valim 提交于
provide a more sementic local variables name in ActiveModel::Validation::Clusivity
-
由 Rafael Mendonça França 提交于
Fetch value(s) from stringified options in tags that stringify options
-
由 Steven Yang 提交于
provide a more sementicthe local variables name for ActiveModel::Validations::Clusivity#include? method the original name `exclusion` is a bit confusing when using with the method `inclusion_method` rename it to a more logic neutral name.
-
由 Steve Klabnik 提交于
remove deprecated implicit join references
-
由 Steve Klabnik 提交于
Update a broken link into the fixtures' template [ci skip]
-
由 Robin Dupret 提交于
-
由 Jon Rowe 提交于
-
由 Yves Senn 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
request thread to return up the stack before the instance variable is assigned. Synchronize so that the ivar is assigned before the other thread can activate. fixes #10984
-
由 Vijay Dev 提交于
Adding documentation to the Rails initialization guide.
-
- 28 6月, 2013 25 次提交
-
-
由 Carlos Antonio da Silva 提交于
Omit turbolinks configuration completely on skip_javascript generator option
-
由 Carlos Antonio da Silva 提交于
ActiveRecord find_in_batches should work without logger When I set logger to nil both methods from Batches module find_in_batches or find_each should work anyway.
-
由 Nikita Fedyashev 提交于
-
由 Carlos Antonio da Silva 提交于
In 94924dc3 the internal default_scope implementation has changed making it simpler to follow, meaning that the old usage of with_default_scope has been removed. With that, order_values was the same argument for both calls to find_first_with_limit, so remove it and use the existent attribute for the sake of clarity/simplification.
-
由 Dmitry Polushkin 提交于
-
由 Jon Leighton 提交于
The previous implementation was necessary in order to support stuff like: class Post < ActiveRecord::Base default_scope where(published: true) scope :ordered, order("created_at") end If we didn't evaluate the default scope at the last possible moment before sending the SQL to the database, it would become impossible to do: Post.unscoped.ordered This is because the default scope would already be bound up in the "ordered" scope, and therefore wouldn't be removed by the "Post.unscoped" part. In 4.0, we have deprecated all "eager" forms of scopes. So now you must write: class Post < ActiveRecord::Base default_scope { where(published: true) } scope :ordered, -> { order("created_at") } end This prevents the default scope getting bound up inside the "ordered" scope, which means we can now have a simpler/better/more natural implementation of default scoping. A knock on effect is that some things that didn't work properly now do. For example it was previously impossible to use #except to remove a part of the default scope, since the default scope was evaluated after the call to #except.
-
由 Carlos Antonio da Silva 提交于
Adding additional plugins to debugging guide [ci skip]
-
由 Carlos Antonio da Silva 提交于
Thanks @lintzchiang. [ci skip]
-
由 Jon Leighton 提交于
For example: class Post < ActiveRecord::Base default_scope -> { where published: true } end class Comment belongs_to :post end When calling `Comment.join(:post)`, we expect to receive only comments on published posts, since that is the default scope for posts. Before this change, the default scope from `Post` was not applied, so we'd get comments on unpublished posts.
-
由 Jon Leighton 提交于
Oops. We need to estalish/remove the connection in the setup/teardown, else it messes with the fixtures.
-
由 Jon Leighton 提交于
Clearly nobody uses this except me. It's fast people!
-
由 Jon Leighton 提交于
Remove depreacted finders
-
由 Akira Matsuda 提交于
-
由 Drew Dara-Abrams 提交于
-
由 Carlos Antonio da Silva 提交于
Remove deprecation warning from AttributeMethodsMatcher
-
由 Łukasz Strzałkowski 提交于
They were deprecated in 4.0, planned to remove in 4.1
-
由 Paul Nikitochkin 提交于
-
由 Yves Senn 提交于
Asking user to declare post resource in getting start guide
-
由 Paul Nikitochkin 提交于
-
由 Carlos Antonio da Silva 提交于
Remove deprecated attr_protected/accessible
-
由 Carlos Antonio da Silva 提交于
-
由 Łukasz Strzałkowski 提交于
Rails 4.0 has removed attr_protected and attr_accessible feature in favor of Strong Parameters.
-
由 Carlos Antonio da Silva 提交于
Remove passing the prompt to grouped_options_for_select as an argument, because it was deprecated.
-
由 kennyj 提交于
-
由 Yves Senn 提交于
Fix documentation for grouped_collection_select
-