kotovalexarian-likes-github
/
rails--rails
mirror of https://github.com/rails/rails.git
1
0
Fork 0
Code Releases Activity
rails--rails/railties/CHANGELOG.md

33 lines
1.2 KiB
Markdown
Raw Normal View History

Use local variables in _form.html.erb generated by scaffold generator. It seems a good idea to use local variables in generated partials instead of using instance variables. Before <%= render 'form' %> After <%= render 'form', product: @product %>
2013-12-21 06:09:52 +00:00
* Use local variables in `_form.html.erb` partial generated by scaffold.
*Andrew Kozlov*
Add config to halt callback chain on return false This stems from [a comment](rails#17227 (comment)) by @dhh. In summary: * New Rails 5.0 apps will not accept `return false` as a way to halt callback chains, and will not display a deprecation warning. * Existing apps ported to Rails 5.0 will still accept `return false` as a way to halt callback chains, albeit with a deprecation warning. For this purpose, this commit introduces a Rails configuration option: ```ruby config.active_support.halt_callback_chains_on_return_false ``` For new Rails 5.0 apps, this option will be set to `false` by a new initializer `config/initializers/callback_terminator.rb`: ```ruby Rails.application.config.active_support.halt_callback_chains_on_return_false = false ``` For existing apps ported to Rails 5.0, the initializers above will not exist. Even running `rake rails:update` will not create this initializer. Since the default value of `halt_callback_chains_on_return_false` is set to `true`, these apps will still accept `return true` as a way to halt callback chains, displaying a deprecation warning. Developers will be able to switch to the new behavior (and stop the warning) by manually adding the line above to their `config/application.rb`. A gist with the suggested release notes to add to Rails 5.0 after this commit is available at https://gist.github.com/claudiob/614c59409fb7d11f2931
2014-12-24 08:58:19 +00:00
* Add `config/initializers/callback_terminator.rb`
Newly generated Rails apps have a new initializer called
`callback_terminator.rb` which sets the value of the configuration option
`config.active_support.halt_callback_chains_on_return_false` to `false`.
As a result, new Rails apps do not halt callback chains when a callback
returns `false`; only when they are explicitly halted with `throw(:abort)`.
The terminator is *not* added when running `rake rails:update`, so returning
`false` will still work on old apps ported to Rails 5, displaying a
deprecation warning to prompt users to update their code to the new syntax.
*claudiob*
Merge pull request #18309 from PaBLoX-CL/fix-fixtures-references Generated fixtures won't use parent_id when generated with parent:references
2015-01-03 02:01:30 +00:00
* Generated fixtures won't use the id when generated with references attributes.
*Pablo Olmos de Aguilera Corradini*
Add --skip-action-mailer (or -M) to rails generate
2014-12-31 13:10:26 +00:00
* Add `--skip-action-mailer` option to the app generator.
*claudiob*
actually autoload all second-level directories called `app/*/concerns`
2014-12-26 17:29:53 +00:00
* Autoload any second level directories called `app/*/concerns`.
*Alex Robbin*
Start Rails 5 development :tada: We will support only Ruby >= 2.1. But right now we don't accept pull requests with syntax changes to drop support to Ruby 1.9.
2014-11-28 17:00:06 +00:00
Please check [4-2-stable](https://github.com/rails/rails/blob/4-2-stable/railties/CHANGELOG.md) for previous changes.