[Rails-core] [ANN] Rails 6.0.2.1 has been released!

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 6.0.2.1 has been released. This is a 
complementary release to
rack in order to address 
[CVE-2019-16782](https://www.openwall.com/lists/oss-security/2019/12/18/2).


## CHANGES since 6.0.2

To view the changes for each gem, please read the changelogs on GitHub:
* [Action Cable 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.1/actioncable/CHANGELOG.md)
* [Action Mailbox 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.1/actionmailbox/CHANGELOG.md)
* [Action Mailer 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.1/actionmailer/CHANGELOG.md)
* [Action Pack 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.1/actionpack/CHANGELOG.md)
* [Action Text 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.1/actiontext/CHANGELOG.md)
* [Action View 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.1/actionview/CHANGELOG.md)
* [Active Job 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.1/activejob/CHANGELOG.md)
* [Active Model 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.1/activemodel/CHANGELOG.md)
* [Active Record 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.1/activerecord/CHANGELOG.md)
* [Active Storage 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.1/activestorage/CHANGELOG.md)
* [Active Support 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.1/activesupport/CHANGELOG.md)
* [Railties 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.1/railties/CHANGELOG.md)

To see a summary of changes, please read the release on GitHub:

[6.0.2.1 CHANGELOG](https://github.com/rails/rails/releases/tag/v6.0.2.1)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v6.0.2...v6.0.2.1).

## SHA-256

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-256 hashes.

Here are the checksums for 6.0.2.1:

```
$ shasum -a 256 *-6.0.2.1.gem
3eedea1285b08d40762a14a122dc5a9c1d6226526f8380dc4ac0d0f4ef086dbe 
actioncable-6.0.2.1.gem
6132861d7706cefed207817d6a097e3e991e5656bdefd5b2c927e88465b957f7 
actionmailbox-6.0.2.1.gem
13e6eb571bc3764859982d5b3f19f43c88969e99cf5fa4b42696d962b85d2d84 
actionmailer-6.0.2.1.gem
df65fc4db1eb21dad71a0c73b9acf21373644580787e2eecd68fb6244af95ebd 
actionpack-6.0.2.1.gem
7857e4f1242ca2064d0b24154fb1d2d05537e24ec78b31ccd51eab7549459c09 
actiontext-6.0.2.1.gem
ccc69763b6d02069a2c5fef62a08d247620e0f9213ce3eaaa79118384141230c 
actionview-6.0.2.1.gem
11dc8701c7d5b80572786e928e264f42cb1ab75b07957955f41d4d367074b0cd 
activejob-6.0.2.1.gem
6d138b1e3e5f009b5fa9a0587f65f25ff58ef42e6a95a3f720fc53caa2aaf84b 
activemodel-6.0.2.1.gem
083928e6fda8b886f24c198d37a6e9e0a077c1bf178ae76668a973175b6b578b 
activerecord-6.0.2.1.gem
e88e5ae590df2fcf7fe3cf4bdd1822dc95841dd1c10fcb5fe26cb66799ce235a 
activestorage-6.0.2.1.gem
817e19e0ce4bc8c6afc63ed064ea84d0e3c8a2ee3d8fb1bb86ab39670c7ca6b5 
activesupport-6.0.2.1.gem
32a07bc27a22c80752847936aa52497c5d97de9c577b1120a2e897dda77f93b0 
rails-6.0.2.1.gem
8f6b9622975fc0f4807770b0633c9998c54ff59a98045a78f6fab110d87bcd66 
railties-6.0.2.1.gem
```

As always, huge thanks to the many contributors who helped with this release.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rubyonrails-core/4eeea6b5-e1c6-468c-a9e3-0ec0d5f9ec41%40www.fastmail.com.

[Rails-core] [ANN] Rails 5.2.4.1 has been released!

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 5.2.4.1 has been released. This is a 
complementary release to
rack in order to address 
[CVE-2019-16782](https://www.openwall.com/lists/oss-security/2019/12/18/2).


## CHANGES since 5.2.4

To view the changes for each gem, please read the changelogs on GitHub:
* [Action Cable 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.4.1/actioncable/CHANGELOG.md)
* [Action Mailer 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.4.1/actionmailer/CHANGELOG.md)
* [Action Pack 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.4.1/actionpack/CHANGELOG.md)
* [Action View 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.4.1/actionview/CHANGELOG.md)
* [Active Job 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.4.1/activejob/CHANGELOG.md)
* [Active Model 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.4.1/activemodel/CHANGELOG.md)
* [Active Record 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.4.1/activerecord/CHANGELOG.md)
* [Active Storage 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.4.1/activestorage/CHANGELOG.md)
* [Active Support 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.4.1/activesupport/CHANGELOG.md)
* [Railties 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.4.1/railties/CHANGELOG.md)

To see a summary of changes, please read the release on GitHub:

[5.2.4.1 CHANGELOG](https://github.com/rails/rails/releases/tag/v5.2.4.1)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v5.2.4...v5.2.4.1).

## SHA-256

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-256 hashes.

Here are the checksums for 5.2.4.1:

```
$ shasum -a 256 *-5.2.4.1.gem
95531ad4731ff341e0df4bff722bc28cf534ca9ed9e00d8a4949474225abe5fb 
actioncable-5.2.4.1.gem
aad99ddae83c22162ba580fc0efe10611bb407832605c21e3ff540ef071e7cb5 
actionmailer-5.2.4.1.gem
5f9cfff904e6d8ed5bd9439a76639e22393308a295c13d663a4622e085a9b738 
actionpack-5.2.4.1.gem
327e504aea3cfd7484c9ec059b7e58faad96be65379a2da959ee336444f7d342 
actionview-5.2.4.1.gem
2141876d50219726ea17b9d8aa8604e6a8fc555fb6230d7987a422e6981b924c 
activejob-5.2.4.1.gem
a1df0522b937364f1ff7f748457644de1863dfba4b4bf01386fd8270bef7e169 
activemodel-5.2.4.1.gem
2fdbe670205b040f0de64198bdbb4093857a32a409e37ba9ade08c20af6965dc 
activerecord-5.2.4.1.gem
ee841d3c038cc45f393bc384be8afc8f4629587411f3eb6b396821b4429aa835 
activestorage-5.2.4.1.gem
57874366b06882ad0c0a0557640851aef13afec19bd4d6c2ee286c9d4eb7b452 
activesupport-5.2.4.1.gem
402c80f8533052bb9f62e9c61aad9a559b96c04961ddda93151852b8f8572885 
rails-5.2.4.1.gem
0b6b0ec65aedae1f3627b05091d63a55bfabd214f483389a9096332dbdc71ac7 
railties-5.2.4.1.gem
```

As always, huge thanks to the many contributors who helped with this release.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rubyonrails-core/21b4fab0-5aec-4a0f-8f4d-d52c87250a02%40www.fastmail.com.

[Rails-core] [ANN] Rails 6.0.2 has been released!

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 6.0.2 has been released.


## CHANGES since 6.0.1

To view the changes for each gem, please read the changelogs on GitHub:
* [Action Cable 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2/actioncable/CHANGELOG.md)
* [Action Mailbox 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2/actionmailbox/CHANGELOG.md)
* [Action Mailer 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2/actionmailer/CHANGELOG.md)
* [Action Pack 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2/actionpack/CHANGELOG.md)
* [Action Text 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2/actiontext/CHANGELOG.md)
* [Action View 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2/actionview/CHANGELOG.md)
* [Active Job 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2/activejob/CHANGELOG.md)
* [Active Model 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2/activemodel/CHANGELOG.md)
* [Active Record 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2/activerecord/CHANGELOG.md)
* [Active Storage 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2/activestorage/CHANGELOG.md)
* [Active Support 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2/activesupport/CHANGELOG.md)
* [Railties 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2/railties/CHANGELOG.md)

To see a summary of changes, please read the release on GitHub:

[6.0.2 CHANGELOG](https://github.com/rails/rails/releases/tag/v6.0.2)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v6.0.1...v6.0.2).

## SHA-256

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-256 hashes.

Here are the checksums for 6.0.2:

```
$ shasum -a 256 *-6.0.2.gem
f26e7cb2f47745881de3a88866dae9d40f28f0b3a810ebf3eb84f394cbedcf36 
actioncable-6.0.2.gem
5f6801d013d9b4ba4acc85560c16710c37b6954e9e0e6bc315c81b8098649787 
actionmailbox-6.0.2.gem
25b6d7033df2e191f3becfcedd31d8b73ed7cb78f03c7b8bb1a8c6b5c8209079 
actionmailer-6.0.2.gem
0bf8831ba14cb9b79845a36377e87d9440f78e99694da46b062ee536e97d 
actionpack-6.0.2.gem
1871a9fe66fa1edf6d46203c208dbe7048ce38ff13b483542e839376bd1f9ca9 
actiontext-6.0.2.gem
64df3b97fd0e366c5f85a96472aeef93695e0edccadc260d3387a164c74fd0ad 
actionview-6.0.2.gem
f11a99a25869c6f3180dc1bd483d0a6d8e5e0cdf3f170af51fe7d76c3b250e2e 
activejob-6.0.2.gem
80428f2eb4392125f94d9e950a7a6e4b4c4fefaf6e31c459590ef41448d4e726 
activemodel-6.0.2.gem
e4970c40936d9e90337ea0f2961e5e3704016b8da9ba1ef55dd921f4a6ddc0f0 
activerecord-6.0.2.gem
ba4d646de7916bd06ebd2af906bec7d0a3e656ddd21b8edb71984e26b3875263 
activestorage-6.0.2.gem
ff7f8b1f6054e604a0e7a35fa3636555cddebf1867c9e51b866271556fb934af 
activesupport-6.0.2.gem
b5223754088b3adfca6608a1901fbd7813b4b994af4ec514accd0b3b5ce05d0b rails-6.0.2.gem
8a7105ed97b5605c2443dea3c6f2b9c87bcbe01aed6cc7abe982bccdd7e1ff52 
railties-6.0.2.gem
```

As always, huge thanks to the many contributors who helped with this release.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rubyonrails-core/0c18ee81-7180-4159-a9b1-8f9f5381b110%40www.fastmail.com.

[Rails-core] [ANN] Rails 6.0.2.rc2 has been released!

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 6.0.2.rc2 has been released.

If no regressions are found, expect the final release on Friday, December 12, 
2019.
If you find one, please open an [issue on 
GitHub](https://github.com/rails/rails/issues/new)
and mention me (@rafaelfranca) on it, so that we can fix it before the final 
release.

## CHANGES since 6.0.1

To view the changes for each gem, please read the changelogs on GitHub:
* [Action Cable 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.rc2/actioncable/CHANGELOG.md)
* [Action Mailbox 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.rc2/actionmailbox/CHANGELOG.md)
* [Action Mailer 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.rc2/actionmailer/CHANGELOG.md)
* [Action Pack 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.rc2/actionpack/CHANGELOG.md)
* [Action Text 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.rc2/actiontext/CHANGELOG.md)
* [Action View 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.rc2/actionview/CHANGELOG.md)
* [Active Job 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.rc2/activejob/CHANGELOG.md)
* [Active Model 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.rc2/activemodel/CHANGELOG.md)
* [Active Record 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.rc2/activerecord/CHANGELOG.md)
* [Active Storage 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.rc2/activestorage/CHANGELOG.md)
* [Active Support 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.rc2/activesupport/CHANGELOG.md)
* [Railties 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.rc2/railties/CHANGELOG.md)

To see a summary of changes, please read the release on GitHub:

[6.0.2.rc2 CHANGELOG](https://github.com/rails/rails/releases/tag/v6.0.2.rc2)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v6.0.1...v6.0.2.rc2).

## SHA-256

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-256 hashes.

Here are the checksums for 6.0.2.rc2:

```
$ shasum -a 256 *-6.0.2.rc2.gem
201051352bd868c379fc76d59b847766ea0af4b168af808ba1e0269d6b939583 
actioncable-6.0.2.rc2.gem
a158bc7909e33fee990e41fe0c010fd2750b3ae33d71668fd2e9b8985277e6bd 
actionmailbox-6.0.2.rc2.gem
35dcd9231ba61ad072d2123d6aa2cac67cce4d8393530d5d8cd4916b16e3801c 
actionmailer-6.0.2.rc2.gem
23b23cbf12cb8ec1b1373276ee37f7f32691500667fd9e14c0bb4848057bd15b 
actionpack-6.0.2.rc2.gem
a6246e525e110de4bea18e82da4d3b7538fdc308949dde250df986175b911d8e 
actiontext-6.0.2.rc2.gem
215cf27ebe42d8991bf4151fc02e4fd043b7a486890cec7faa15387b6847d074 
actionview-6.0.2.rc2.gem
47959894de499ea57043c77d06fc492b29f2b448e65c76cda779968a43b24aaa 
activejob-6.0.2.rc2.gem
042f0409d8b109d96246b45f255515d0a98533bab44bc15af7c511c8f4893486 
activemodel-6.0.2.rc2.gem
123a2959e6dc9f87e7b39ca436248dac7a40415e6d2b6a9266418bb24bcb02ca 
activerecord-6.0.2.rc2.gem
2e652d35e7bca6ea5e72a979c6d08534cb53e9ff647bf7e05f4ba2c525a8b721 
activestorage-6.0.2.rc2.gem
007f106c1419b6cfdc0a82cac72550f302821d53ca74a1ffafaf11eb93fb0ef3 
activesupport-6.0.2.rc2.gem
5cb22ec58dd58fb79fa1f3da50adff4692a41cf19ff4a2fa6cde482885d9f310 
rails-6.0.2.rc2.gem
c33a3986cfc1dda1f561abb92a2ef9826fa0b574db42bb2b2f51b01f0cf0517b 
railties-6.0.2.rc2.gem
```

As always, huge thanks to the many contributors who helped with this release.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rubyonrails-core/a8ce466a-e87d-40dc-a404-3fee1a14db47%40www.fastmail.com.

[Rails-core] [ANN] Rails 5.2.4 has been released

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 5.2.4 has been released.


## CHANGES since 5.2.3

To view the changes for each gem, please read the changelogs on GitHub:
* [Action Cable 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.4/actioncable/CHANGELOG.md)
* [Action Mailer 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.4/actionmailer/CHANGELOG.md)
* [Action Pack 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.4/actionpack/CHANGELOG.md)
* [Action View 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.4/actionview/CHANGELOG.md)
* [Active Job 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.4/activejob/CHANGELOG.md)
* [Active Model 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.4/activemodel/CHANGELOG.md)
* [Active Record 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.4/activerecord/CHANGELOG.md)
* [Active Storage 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.4/activestorage/CHANGELOG.md)
* [Active Support 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.4/activesupport/CHANGELOG.md)
* [Railties 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.4/railties/CHANGELOG.md)

To see a summary of changes, please read the release on GitHub:

[5.2.4 CHANGELOG](https://github.com/rails/rails/releases/tag/v5.2.4)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v5.2.3...v5.2.4).

## SHA-256

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-256 hashes.

Here are the checksums for 5.2.4:

```
$ shasum -a 256 *-5.2.4.gem
0ba74e3b94e4712f3d754125e494f45e5240af8f4c8c8f0f167dff3b0e0a3a96 
actioncable-5.2.4.gem
c85a6f665f5d6ed48104c9984a928851dd490a49e2ef866a71530c5a62dfd87c 
actionmailer-5.2.4.gem
0ccecdc86c8c98adf5a16e2a5bf55379a16e845db94bc12899f052d25ad48d91 
actionpack-5.2.4.gem
19b1a9c0a26bb8d0c1cfec353784e518a61dd7e218a29f5e309c4c7d7bc5beac 
actionview-5.2.4.gem
8f4baa59887eafb63b7a9f0fc194101e4c996a3210815a151270d08a0d2f22d8 
activejob-5.2.4.gem
f87e407f1fc3b04c3ee680278a5af5c2b3263d2d87f8e96d555249c7bbe3f479 
activemodel-5.2.4.gem
cd6eca48d5cb6859c5e09dea5ec11677791af26218c269cef8936bc0b4923a18 
activerecord-5.2.4.gem
1fae89ac78f965f590d6867b3bc1546fb662b5fde780f38789ac3ad61ed8e40c 
activestorage-5.2.4.gem
b826f53ae52f1250edf56d254a839ca5df7c0a9d8e8c9334629d6bbd0eb61bce 
activesupport-5.2.4.gem
3abc0d1c5a6a87821ed73d0f523fbb63e09610dbdfd7f8b948e14a15f7749481 rails-5.2.4.gem
5c3a7788700b99c75be9041cab79d92a89d8c76173b232753d7ea7e6e43233ee 
railties-5.2.4.gem
```

As always, huge thanks to the many contributors who helped with this release.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rubyonrails-core/8a08348d-e826-4ba5-a329-ab19e6dff9fe%40www.fastmail.com.

[Rails-core] [ANN] Rails 6.0.2.rc1 has been released

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 6.0.2.rc1 has been released.

If no regressions are found, expect the final release on Monday, December 2, 
2019.
If you find one, please open an [issue on 
GitHub](https://github.com/rails/rails/issues/new)
and mention me (@rafaelfranca) on it, so that we can fix it before the final 
release.

## CHANGES since 6.0.1

To view the changes for each gem, please read the changelogs on GitHub:
* [Action Cable 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.rc1/actioncable/CHANGELOG.md)
* [Action Mailbox 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.rc1/actionmailbox/CHANGELOG.md)
* [Action Mailer 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.rc1/actionmailer/CHANGELOG.md)
* [Action Pack 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.rc1/actionpack/CHANGELOG.md)
* [Action Text 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.rc1/actiontext/CHANGELOG.md)
* [Action View 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.rc1/actionview/CHANGELOG.md)
* [Active Job 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.rc1/activejob/CHANGELOG.md)
* [Active Model 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.rc1/activemodel/CHANGELOG.md)
* [Active Record 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.rc1/activerecord/CHANGELOG.md)
* [Active Storage 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.rc1/activestorage/CHANGELOG.md)
* [Active Support 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.rc1/activesupport/CHANGELOG.md)
* [Railties 
CHANGELOG](https://github.com/rails/rails/blob/v6.0.2.rc1/railties/CHANGELOG.md)

To see a summary of changes, please read the release on GitHub:

[6.0.2.rc1 CHANGELOG](https://github.com/rails/rails/releases/tag/v6.0.2.rc1)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v6.0.1...v6.0.2.rc1).

## SHA-256

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-256 hashes.

Here are the checksums for 6.0.2.rc1:

```
$ shasum -a 256 *-6.0.2.rc1.gem
f7f620f3042bc73f8e461deab8005f089dc58adcbcf5ab8112878245ad62db75 
actioncable-6.0.2.rc1.gem
98860fedcb06a53bf0bb6367810f148bfd387fab2461aaa3511966c332ccaba7 
actionmailbox-6.0.2.rc1.gem
30c442e289504fd4847341c702a2096954218107b8dd033c9e460ab6fb812e28 
actionmailer-6.0.2.rc1.gem
8ef626574ee988c0d59fcf03b6e60202fda2797bc387cf85922011053bcb7951 
actionpack-6.0.2.rc1.gem
4fa0062cdc66ca2fa30d28d1681b22fa245cbd4fe1cc7219573bc790131f3f95 
actiontext-6.0.2.rc1.gem
5760324a0ea085391c97cd072dd39a3aa352f40935308344f2e19ac7f244b772 
actionview-6.0.2.rc1.gem
48c91cf9ee11ba60519cd7daca0914c0310491b69b1c03b5ca5a0383af29f863 
activejob-6.0.2.rc1.gem
694d5c84aa0cc7a8b438dc6ecb18b8b22b69773aced6d5982b00941d5f905dfe 
activemodel-6.0.2.rc1.gem
399098bb60e1ee3897ee82db7ec98152d8465a08917f3e5dcccb4085fcb06904 
activerecord-6.0.2.rc1.gem
c8ce7396d623e794bb2568b6c2d6f7b8b2c26b0246547b9f7e91c3c55f56be36 
activestorage-6.0.2.rc1.gem
c1ba538d3ac80e1a3aaf2c8ff36db215f0a1fcd7a1908df8de5cad56f711efd0 
activesupport-6.0.2.rc1.gem
64981b76140ca930e008f8e58879ec963a8ad5386fb894d58e655b491a7bd1fd 
rails-6.0.2.rc1.gem
37f224e83d39408dbc240549ab866b11bb53409563cb677ee65bd58bc39cfcef 
railties-6.0.2.rc1.gem
```

As always, huge thanks to the many contributors who helped with this release.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rubyonrails-core/b5bf27b2-b92e-48e2-ad07-0a17713ef0d5%40www.fastmail.com.

[Rails-core] [ANN] Rails 5.2.4.rc1 has been released!

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 5.2.4.rc1 has been released.

This is going to be the last bug fix release of the 5.2 series, so please test 
the releases candidates
and report regressions so we can fix before the final release.

If no regressions are found, expect the final release on Wednesday, November 
27, 2019.
If you find one, please open an [issue on 
GitHub](https://github.com/rails/rails/issues/new)
and mention me (@rafaelfranca) on it, so that we can fix it before the final 
release.

## CHANGES since 5.2.3

To view the changes for each gem, please read the changelogs on GitHub:
* [Action Cable 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.4.rc1/actioncable/CHANGELOG.md)
* [Action Mailer 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.4.rc1/actionmailer/CHANGELOG.md)
* [Action Pack 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.4.rc1/actionpack/CHANGELOG.md)
* [Action View 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.4.rc1/actionview/CHANGELOG.md)
* [Active Job 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.4.rc1/activejob/CHANGELOG.md)
* [Active Model 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.4.rc1/activemodel/CHANGELOG.md)
* [Active Record 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.4.rc1/activerecord/CHANGELOG.md)
* [Active Storage 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.4.rc1/activestorage/CHANGELOG.md)
* [Active Support 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.4.rc1/activesupport/CHANGELOG.md)
* [Railties 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.4.rc1/railties/CHANGELOG.md)

To see a summary of changes, please read the release on GitHub:

[5.2.4.rc1 CHANGELOG](https://github.com/rails/rails/releases/tag/v5.2.4.rc1)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v5.2.3...v5.2.4.rc1).

## SHA-256

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-256 hashes.

Here are the checksums for 5.2.4.rc1:

```
$ shasum -a 256 *-5.2.4.rc1.gem
71c875fc798edf11372e801319dc0f85b22a6c3b15ee269f7e354bbd0b525df3 
actioncable-5.2.4.rc1.gem
c623597a1ca76930cb28e5d07085b0ce5e89d465fbc5784753344633898d5118 
actionmailer-5.2.4.rc1.gem
45393dfd757daa4e375846199fde5fce6713eb85793e441cc7b2cd091f543a14 
actionpack-5.2.4.rc1.gem
74a0508940d34bad7c3f84668c20d0277f9cbdffc13c3cf55ee754c33afa1612 
actionview-5.2.4.rc1.gem
12baf95010f778044d70ae2b3fae5755dc89113576082dbfc76f88b2a32ee70b 
activejob-5.2.4.rc1.gem
7cd8ac1e7739181c83ad63e164a4e92d058f5b57dc040e2f03a724243dc6cb2a 
activemodel-5.2.4.rc1.gem
088d6ebe600b8147ca0764c688ea5c184c3127dd8dfc4c41d36778335c8e4d85 
activerecord-5.2.4.rc1.gem
0cc29d1439c4302f7515a9f703a4672b7a1764b67650074cd00c83914106daab 
activestorage-5.2.4.rc1.gem
138926da539471bb91fd8270ded2f44aeafafcf45ede8ee68dee63873b1d0b4e 
activesupport-5.2.4.rc1.gem
c9f9a2381a465888619736d6dd5108c795bbffabf0f1cd7cf49fbac26e4e88c8 
rails-5.2.4.rc1.gem
e455f200dd872c710684db8e45b982a5d9de6c7e481c397715d1a232918a95db 
railties-5.2.4.rc1.gem
```

As always, huge thanks to the many contributors who helped with this release.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rubyonrails-core/beef9ff9-3abb-4e48-ac15-8f43364618d7%40www.fastmail.com.

Re: [Rails-core] Add origin as part of `redirect_to.action_controller` Instrumentation

[Rafael Mendonça França]

Please open the PR.

On Fri, Nov 22, 2019, at 3:09 PM, Austin Story wrote:
> Requesting to extend an existing feature
> 
> 
> I would like to add 'origin' to the 'redirect_to.action_controller' 
> instrumentation. This change will allow subscribers to the notification to 
> report on both where we are going and where we are coming from
> 
> https://github.com/rails/rails/compare/master...Austio:add-origin-to-action-controller-redirect-to-instrumentation?expand=1
> 
> A real world use case for this, we have a lot of developers in our code base 
> and would like to know when someone is using redirect_to and dropping 
> `utm_campaign` query params in the process.
> 
> 
> 
> 

> --
>  You received this message because you are subscribed to the Google Groups 
> "Ruby on Rails: Core" group.
>  To unsubscribe from this group and stop receiving emails from it, send an 
> email to rubyonrails-core+unsubscr...@googlegroups.com.
>  To view this discussion on the web visit 
> https://groups.google.com/d/msgid/rubyonrails-core/f67dfe3e-dcdb-4dfb-8e50-d067b7aa3672%40googlegroups.com
>  
> .

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rubyonrails-core/7f2f0e22-8ef9-4ea3-a6ea-c56af9fd302a%40www.fastmail.com.

Re: [Rails-core] Proposal to run spell check on GItHub Actions

[Rafael Mendonça França]

While I agree we should try to avoid typos in our codebase.

Fixing typos It is a very easy and low barrier way to get new contributors, and 
I think this kind of contribution is very welcome, so I’d prefer to not 
discourage or even remove the possibility of people to submit typo PRs.

Maybe, someday, someone start with a PR to fix a typo 
(https://github.com/rails/rails/commit/a0552d653b00e2e5b77e086b155e89fa22e4d6ed 
)
 and end up in the top of this list https://contributors.rubyonrails.org/ 
.

> On Oct 29, 2019, at 21:06, Dana Sherson  wrote:
> 
> Hi friends, in case it's relevant, i've recently built a source-code focused 
> spell checker in ruby https://github.com/robotdana/spellr designed to be part 
> of CI pipelines
> 
> On Tuesday, October 29, 2019 at 6:03:27 PM UTC+11, Masafumi Okura wrote:
> Hi Richard,
> 
> I understand your concern. I'm not really familiar with spell checking on 
> technical documents, so I'd like to stop this discussion here. If I get more 
> familiar with how to introduce informational spell checker, I'll come to give 
> a proposal again.
> 
> On Monday, October 28, 2019 at 3:43:52 AM UTC+9, richard schneeman wrote:
> As someone who has commit to the project merging in spelling corrections 
> takes almost no time. I don't think getting fewer of these PRs would be a 
> huge net win (others with commit might disagree). As an occasional writer of 
> features and docs, it would be nice to get feedback right away that I had 
> made an error, but I find spell checking for technical documentation to be 
> very error-prone. I usually turn it off for my editors due to the sheer 
> volume of false spelling flags. If we did adopt some kind of a spell checker 
> I would want it to be more for information purposes than as a hard blocker. 
> If the accuracy looks good then we could eventually make it mandatory.
> 
> 
> On Sun, Oct 27, 2019 at 9:20 AM Masafumi Okura > wrote:
> Hi,
> 
> This is a proposal related to 
> https://groups.google.com/d/msg/rubyonrails-core/o3wWBsTSbxU/s9X6pJHDBwAJ 
> 
> 
> I see many Pull Requests fixing typos in documents. This can be done mostly 
> automatically by machines.
> I found there's a good tool to find misspells. 
> https://github.com/client9/misspell 
> If we can run this tool on CI, we can reduce the number of Pull Requests just 
> fixing typos.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to rubyonra...@googlegroups.com <>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/rubyonrails-core/cd70b713-02a1-4812-b6f8-01dbdfa7ce01%40googlegroups.com
>  
> .
> 
> 
> -- 
> Richard Schneeman
> https://www.schneems.com 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to rubyonrails-core+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/rubyonrails-core/eb29ae0b-0c1a-4de0-aefe-95a01f9952a9%40googlegroups.com
>  
> .

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rubyonrails-core/BE6E20C5-9043-43BE-8155-D0AE40528FD9%40gmail.com.

Re: [Rails-core] Backport ActiveRecord query cache feature from 6.x to 5.2

[Rafael Mendonça França]

Hello!

With the release of Rails 6.0.0, Rails 5.2 became a security only release. No 
bug fixes or new features are going to be added to 5.2 unless it is for 
security reasons.

See https://edgeguides.rubyonrails.org/maintenance_policy.html#bug-fixes 


> On Oct 18, 2019, at 12:31, Николай Марков  wrote:
> 
> Hello!
> 
> TLDR: I would like to backport https://github.com/rails/rails/pull/35089 
>  ("Invalidate all query caches for 
> current thread") to 5.2-stable branch.
> The issue comes from this patch which enables query cache for all connection 
> pools - https://github.com/rails/rails/pull/28869 
> .
> 
> Longer text:
> I'm using active_record_slave 
>  to read some records from 
> slave database. It uses special abstract model which connects to slave 
> database using establish_connection and all reads go through this model by 
> default.
> 
> My case (consider this happens inside http request/response cycle):
> 
> fetch some record - it will be read from slave and this query will be cached
> delete that record - this query will go through AR::Base.connection_pool to 
> master database and this will clear the cache for this connection pool but 
> not for connection pool of the model for slave database.
> fetch the same record from step №1 using the same query - this will return 
> the record from cache, because all reads go to slave by default.
> AR.uncached cannot be used because it works only for AR::Base.connection_pool.
> 
> Can I make a backport?
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to rubyonrails-core+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/rubyonrails-core/0cf6351a-a8f7-409e-a012-d6f9f11c6d96%40googlegroups.com
>  
> .

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rubyonrails-core/8CFD84E0-6E20-4053-8B10-4E8AAF5F08BB%40gmail.com.

Re: [Rails-core] Question: Is ::Upload used anywhere in Rails?

[Rafael Mendonça França]

I hope this commit answers the question 
https://github.com/rails/rails/commit/fb5f8d4f86a4a08705d6e9b39b44203df22ab50d 
.

> On Aug 8, 2019, at 14:51, Al  wrote:
> 
> Is "::Upload" used anywhere in Rails? Sorbet is asking.
> 
> https://github.com/rails/rails/blob/master/actionpack/lib/action_dispatch.rb 
> 
>  :84: autoload :Upload
> 
> Thanks,
> Al
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to rubyonrails-core+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/rubyonrails-core/17242cbd-2721-4494-9a5a-21f5c2ab46d1%40googlegroups.com
>  
> .

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rubyonrails-core/176331EC-507E-41D7-88F3-5D1C8388BD8A%40gmail.com.

Re: [Rails-core] Deprecate strip_heredoc?

[Rafael Mendonça França]

The squiggly-heredoc operator can't be applied to an already existing
string. That is the only case were you still need strip_heredoc, so unless
we add a way to strip heredocs from an already existent string object to
Ruby we can't deprecated it.

See
https://github.com/rails/rails/commit/89bcca59e91fa9da941de890012872e8288e77b0
for
the reasoning and
https://github.com/rails/rails/blob/6729cef7516207efa1980de65fb4e1c72b4376d1/railties/lib/rails/generators/actions.rb#L330
for one place where we don't have an equivalent method.

Rafael Mendonça França
http://twitter.com/rafaelfranca
https://github.com/rafaelfranca


On Sat, Jun 8, 2019 at 12:28 PM Xavier Noria  wrote:

> +1 too.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/rubyonrails-core/CAM%3DYcdg-5w386piouguCujy8NoKcr0CpHor9zwSrWiZHOuUv7w%40mail.gmail.com
> <https://groups.google.com/d/msgid/rubyonrails-core/CAM%3DYcdg-5w386piouguCujy8NoKcr0CpHor9zwSrWiZHOuUv7w%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rubyonrails-core/CAC9YFze7jD8kc%3DhnCfTjsCa6pJHm2X5DbHZuYBD%3D_pB6ufnVdw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] [Feature] [ActionPack] Add deep_transform_keys to ActionController::StrongParameters

[Rafael Mendonça França]

 for this method.Can you open the PR?
Rafael Mendonça França
http://twitter.com/rafaelfranca
https://github.com/rafaelfranca


On Mon, May 13, 2019 at 6:48 AM Gustavo Gutierrez 
wrote:

> We are currently working with Rails API interacting with a frontend app.
> In order to simplify the interactions with the front app, we are supporting
> parameters and responses with *camelCase*.
>
> When we were implementing this in the Rails API, we encountered that
> *ActionController::StrongParameters* implements *transform_keys *but it
> doesn't implements *deep_transform_keys*, as Hash does.
> This would be a helpful feature for us because we use nested params for
> some requests, and we think it would also make the StrongParams API more
> similar to the Hash API.
>
> Any feedback on this would be very helpful. In AcidTango we have the
> intention to implement this feature if it is considered helpful.
>
> Regards!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/rubyonrails-core/9d0a3810-bf1d-405f-b788-6b840ba00c49%40googlegroups.com
> <https://groups.google.com/d/msgid/rubyonrails-core/9d0a3810-bf1d-405f-b788-6b840ba00c49%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rubyonrails-core/CAC9YFze_yKqgoOF%3D%2BxUJ%2BmBDX03CqYXruNBQwSFbHT85ZwKgYQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] [Feature] Move the "to_param" logic out of ActiveRecord

[Rafael Mendonça França]

> Problem : there's no easy solution to achieve this, because overriding
to_param is global.

Have you considered wrapping the object in a decorator that changes the
`to_param` method to what you want?

url_for(@article)
# => /articles/2019-05-my-breaking-news

url_for(AdminArticleDecorator.new(@article))
# => /admin/articles/12

class AdminArticleDecorator
  def initialize(article)
@artile = article
  end

  def to_param(*)
@article.id
  end
end

Rafael Mendonça França
http://twitter.com/rafaelfranca
https://github.com/rafaelfranca


On Thu, May 9, 2019 at 7:29 PM Romain Goyet 
wrote:

> Hi everyone!
>
> I've been using rails for a while (since rails 2) but never had the
> opportunity to contribute. I'd like to take this opportunity to thank all
> contributors to Rails :)
>
> Anyway, I'm running into some issue with to_param. Consider the case where
> you have a resource that you'd like to route using identifiers that are
> *not* the :id. Currently, the recommended way to achieve that is by
> overriding the #to_param method on the model. I think that's questionable
> design.
>
> Let's consider a simple example : you want to expose the same resource at
> two different routes. For instance, on a blog, you'd want to route articles
> using a slug for SEO on public URLs, and using an id on the admin interface
> because you use like to use ids internally.
>
> /articles/2019-05-my-breaking-news
> /admin/articles/12
>
> Problem : there's no easy solution to achieve this, because overriding
> to_param is global.
>
> Suggested solution : that's actually a routing topic, so it should be
> solve in the routing. I suggest leveraging the "param" routing option to do
> this, and leave the Models alone :)
>
> routes.draw do
>   resources :articles, param: :slug
>   namespace :admin do
> resources :articles
>   end
> end
>
> Currently, this changes the name of the parameter used in the route.
> That's a good start. But it has *no* impact on the named route helpers.
> Namely, url_for(@article) will still use the :id, even though ":slug" has
> been specified.
> I suggest to also change the named route helpers to call
> "@article.#{param}" if a routing param has been specified.
>
> I hope this suggestion makes sense, just let me know :-)
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/rubyonrails-core/eac44ecb-df8d-45f2-ae8d-cb1ad04f94a1%40googlegroups.com
> <https://groups.google.com/d/msgid/rubyonrails-core/eac44ecb-df8d-45f2-ae8d-cb1ad04f94a1%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rubyonrails-core/CAC9YFzd-BbECWXs3wQfRCA_k3vW4X9KtgjEW3kFjamUFAShLTw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] [ANN] Rails 5.1.7 has been released

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 5.1.7 has been released.


## CHANGES since 5.1.6

To view the changes for each gem, please read the changelogs on GitHub:
* [Action Cable CHANGELOG](
https://github.com/rails/rails/blob/v5.1.7/actioncable/CHANGELOG.md)
* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v5.1.7/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v5.1.7/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v5.1.7/actionview/CHANGELOG.md)
* [Active Job CHANGELOG](
https://github.com/rails/rails/blob/v5.1.7/activejob/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v5.1.7/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v5.1.7/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v5.1.7/activesupport/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v5.1.7/railties/CHANGELOG.md)

To see a summary of changes, please read the release on GitHub:

[5.1.7 CHANGELOG](https://github.com/rails/rails/releases/tag/v5.1.7)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v5.1.6...v5.1.7).

## SHA-256

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-256 hashes.

Here are the checksums for 5.1.7:

```
$ shasum -a 256 *-5.1.7.gem
c344a1b4edd4108b93b341343106e73466d8bbf0a79c926a62c74f6b22984ec1
actioncable-5.1.7.gem
f053e043f0e83b7758b56af7fe21aa3ab2f61787e2edc6a1198acc8d3645fbbe
actionmailer-5.1.7.gem
a2406a8346f95294ad9342c1535e2cc4f04e7c084e71359bae224650581bd17f
actionpack-5.1.7.gem
871ca9cae0524e937543510104555c1e8d87f180b14ce0a03fe62c69012a5244
actionview-5.1.7.gem
f44a4691d7fca6b0f08c2dbd5c81110f428d5c8ade9c6a6b8e09c7984741a55c
activejob-5.1.7.gem
709bb03d9c950353e8f70e0ed4f12154c346d492e5bf6ea53b515413c740fc1e
activemodel-5.1.7.gem
5a1f4bf7b5e5c05a3e21e9207f1336eab026b3dfd794a374a4c81cfe8544
activerecord-5.1.7.gem
216db77f40e41dab82328321c375f519de8c898dcc2b88a5319d3608928fd07e
activesupport-5.1.7.gem
8d7f527c446de3f99ec506e6a680c42c38979a44b37beb15f7d451a33e74dcf5
rails-5.1.7.gem
c874ebb682f628cfe075c3b9762d3b2ff1a04585c25a2f4eb3840c4b29d73e72
railties-5.1.7.gem
```

As always, huge thanks to the many contributors who helped with this
release.

Rafael Mendonça França
http://twitter.com/rafaelfranca
https://github.com/rafaelfranca

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] [ANN] Rails 5.2.3 has been released

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 5.2.3 has been released.


## CHANGES since 5.2.2

To view the changes for each gem, please read the changelogs on GitHub:
* [Action Cable CHANGELOG](
https://github.com/rails/rails/blob/v5.2.3/actioncable/CHANGELOG.md)
* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v5.2.3/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v5.2.3/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v5.2.3/actionview/CHANGELOG.md)
* [Active Job CHANGELOG](
https://github.com/rails/rails/blob/v5.2.3/activejob/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v5.2.3/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v5.2.3/activerecord/CHANGELOG.md)
* [Active Storage CHANGELOG](
https://github.com/rails/rails/blob/v5.2.3/activestorage/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v5.2.3/activesupport/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v5.2.3/railties/CHANGELOG.md)

To see a summary of changes, please read the release on GitHub:

[5.2.3 CHANGELOG](https://github.com/rails/rails/releases/tag/v5.2.3)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v5.2.2...v5.2.3).

## SHA-256

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-256 hashes.

Here are the checksums for 5.2.3:

```
$ shasum -a 256 *-5.2.3.gem
755e335b8b064592717157057a647ba1c4d519be2a912f11c3993e8d5c4e8d13
actioncable-5.2.3.gem
8a6fbf3f52243cdc194c289a417856355899bcc99ec2868300a2b26f40f58a96
actionmailer-5.2.3.gem
81830a59e18d7570386a01bb332538ddf0926b5ed7566646ef608a78825751e8
actionpack-5.2.3.gem
9064ef94411d98cf7c7cc0fb179319b92a880f51f8e0671cceaf8081dccb89ec
actionview-5.2.3.gem
faa055b4986b0d3183ebd8169d82ef491dc947e075e777af2f91ead557fc719f
activejob-5.2.3.gem
d04c4367fd41a2d8767be08e9caadc617e6f825025079854562100145b82f055
activemodel-5.2.3.gem
fc6ef79f341d32b5690a7cb5a26245c33c3d2e4a7c99bb7d1c0089549c19c034
activerecord-5.2.3.gem
80cde4c4990c4220b78c24c50f1a6db7d4a954cc36158c0104c283804145205c
activestorage-5.2.3.gem
2856b0036869e89043f5c870a1a99d2c811785130fea4affad83cf971db91b84
activesupport-5.2.3.gem
f9b51b66a91d556d63d36d04449ecc23867683f99531db21eb7a263be2d7ecdc
rails-5.2.3.gem
042388decffb47dab796e4ddb30a2d615047d7c334de7fe47208545e1677c9be
railties-5.2.3.gem
```

As always, huge thanks to the many contributors who helped with this
release.

Rafael Mendonça França
http://twitter.com/rafaelfranca
https://github.com/rafaelfranca

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] [ActiveRecord] [Feature Proposal] Common Table Expression support

[Rafael Mendonça França]

Cool! I think the hard work is already done. But I still find it hard to
justify this in the framework. It is a feature that is out of Rails for
more than 10 years and I personally never needed it working in many
applications through the years so I'm not sure if I want to add that
complexity to the framework and maintain this feature.

We are planing to expose arel as public API sometime in the future so maybe
that would be enough to allow people who wants to use CTE to be able to use
in their application.

Rafael Mendonça França
http://twitter.com/rafaelfranca
https://github.com/rafaelfranca


On Tue, Jan 15, 2019 at 7:41 PM Sean Linsley 
wrote:

> While we’re on the subject, I have a PR to get postgres_ext working with
> Rails 5.2, but need help from someone that has experience with Arel’s
> internals.
>
> https://github.com/danmcclain/postgres_ext/pull/2
>
> Though more broadly I’m of the opinion that most of it should be inlined
> into Rails, and would be happy to work on that effort if it’s welcome.
>
> On Jan 15, 2019, at 6:37 PM, Daniel Heath 
> wrote:
>
> https://rubygems.org/gems/postgres_ext implements this for rails up to
> version 4, and has ~2 million downloads.
>
> https://github.com/kmurph73/ctes_in_my_pg ports the code to rails 5.
>
> There are also numerous blog posts around documenting how to work around
> the issue by dropping down to raw Arel or string interpolation.
>
> eg:
>  *
> http://www.scimedsolutions.com/articles/75-arel-part-ii-common-table-expressions
>  * https://hashrocket.com/blog/posts/recursive-sql-in-activerecord
>  *
> https://sonnym.github.io/2017/06/05/common-table-expressions-in-activerecord-a-case-study-of-quantiles/
>
>
>
> https://www.cockroachlabs.com/blog/cockroachdb-hearts-activerecord-ruby-on-rails/
> also mentions that ActiveRecord uses CTEs internally.
>
> Would you agree that's a suitable level of usage to justify including this
> SQL-99 feature in core ActiveRecord? Or is the complexity likely to be too
> much for the number of users affected?
>
> Thanks,
>
> Daniel Heath
>
> On Wednesday, January 16, 2019 at 11:21:42 AM UTC+11, Rafael Mendonça
> França wrote:
>>
>> Thank you for the feature proposal. It doesn't seem to be difficult to
>> implement this as a gem given most of the APIs you need in able to
>> implement something like this are public.
>>
>> What do you think about implementing this first as a gem and see if there
>> are adoption of this feature before proposing adding to the rails framework?
>>
>> Thanks.
>>
>> Rafael Mendonça França
>> http://twitter.com/rafaelfranca
>> https://github.com/rafaelfranca
>>
>>
>> On Tue, Jan 15, 2019 at 7:12 PM Daniel Heath 
>> wrote:
>>
>>> I'd like to be able to use my ActiveRecord scopes in a CTE for another
>>> scope.
>>>
>>> Proposed syntax
>>>
>>>
>>> class Post < ActiveRecord::Base
>>> has_many :comments
>>> end
>>>
>>> class Comment < ActiveRecord::Base
>>> belongs_to :post
>>> end
>>>
>>> Post.with(Comment.select(:post_id), name: :post_ids, recursive:
>>> false).where(id: {post_ids: :post_id})
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Would a patch supporting this syntax be accepted?
>>>
>>> Thanks,
>>>
>>> Daniel Heath
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Ruby on Rails: Core" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to rubyonrails-co...@googlegroups.com.
>>> To post to this group, send email to rubyonra...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/rubyonrails-core.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop

Re: [Rails-core] [ActiveRecord] [Feature Proposal] Common Table Expression support

[Rafael Mendonça França]

Thank you for the feature proposal. It doesn't seem to be difficult to
implement this as a gem given most of the APIs you need in able to
implement something like this are public.

What do you think about implementing this first as a gem and see if there
are adoption of this feature before proposing adding to the rails framework?

Thanks.

Rafael Mendonça França
http://twitter.com/rafaelfranca
https://github.com/rafaelfranca


On Tue, Jan 15, 2019 at 7:12 PM Daniel Heath 
wrote:

> I'd like to be able to use my ActiveRecord scopes in a CTE for another
> scope.
>
> Proposed syntax
>
>
> class Post < ActiveRecord::Base
> has_many :comments
> end
>
> class Comment < ActiveRecord::Base
> belongs_to :post
> end
>
> Post.with(Comment.select(:post_id), name: :post_ids, recursive:
> false).where(id: {post_ids: :post_id})
>
>
>
>
>
>
>
>
>
>
>
>
>
> Would a patch supporting this syntax be accepted?
>
> Thanks,
>
> Daniel Heath
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] [ANN] Rails 5.2.2.rc1 has been released

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 5.2.2.rc1 has been released.

If no regressions are found, expect the final release on Monday, December 3, 
2018.
If you find one, please open an [issue on 
GitHub](https://github.com/rails/rails/issues/new)
and mention me (@rafaelfranca) on it, so that we can fix it before the final 
release.

## CHANGES since 5.2.1

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Cable 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.2.rc1/actioncable/CHANGELOG.md)
* [Action Mailer 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.2.rc1/actionmailer/CHANGELOG.md)
* [Action Pack 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.2.rc1/actionpack/CHANGELOG.md)
* [Action View 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.2.rc1/actionview/CHANGELOG.md)
* [Active Job 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.2.rc1/activejob/CHANGELOG.md)
* [Active Model 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.2.rc1/activemodel/CHANGELOG.md)
* [Active Record 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.2.rc1/activerecord/CHANGELOG.md)
* [Active Storage 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.2.rc1/activestorage/CHANGELOG.md)
* [Active Support 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.2.rc1/activesupport/CHANGELOG.md)
* [Railties 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.2.rc1/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v5.2.1...v5.2.2.rc1).

## SHA-256

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-256 hashes.

Here are the checksums for 5.2.2.rc1:

```
$ shasum -a 256 *-5.2.2.rc1.gem
c412268c40fc61c16480952c801261d4901c2b0ca81518c6b8ed1c619e38cbe4 
actioncable-5.2.2.rc1.gem
33dcd916c7097823a598e02ee27af657f452c9e1ca5b56d5e8d33871870e84d5 
actionmailer-5.2.2.rc1.gem
ad0178b8e4115eb7b6447f536c24f7725a6022a615a0d9dca1fca055856a6bba 
actionpack-5.2.2.rc1.gem
f0202029b41eeda234e52136191604a52adda23445722172ec2398efe830efd1 
actionview-5.2.2.rc1.gem
56102eeb75e9a29d400a648334f2f7e16f21948a608abd448c4663235752a7ea 
activejob-5.2.2.rc1.gem
cca50c361514be3e901b695cece93ae5230a9018305d336b683fd35a1e97832e 
activemodel-5.2.2.rc1.gem
7bded9a0bfe31eca3df543e59945cf16e3d0d1b32908d879fa1f9469a9cbd3e3 
activerecord-5.2.2.rc1.gem
5cd7d2938d615637201326083edcb5b832254dec3a64638440777c34f1ad030c 
activestorage-5.2.2.rc1.gem
bcd01d80cd4863368d3c3c8914527170b488b354611eeecd6e57553019c776ef 
activesupport-5.2.2.rc1.gem
8e1fdbabab9eae02fc76078eea1dc1d975a9be8cbcfeda4395137503da3f1bf7 
rails-5.2.2.rc1.gem
1d9950a611acb8fef50ba1477efa3e4730d713db55f834bdccd12fd950f2de51 
railties-5.2.2.rc1.gem
```

As always, huge thanks to the many contributors who helped with this release.


Rafael França

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] autoload_reloader by Shopify

[Rafael Mendonça França]

When the author wrote that gem the idea was to integrate it to Rails. When
I open sourced that gem the idea was to give the Rails core members
material to review and experiment.

So, yes, we are looking on it.
On Thu, Nov 1, 2018 at 19:03  wrote:

> Hi,
>
> I was wondering if anybody thinks that the gem has a good approach for
> loading constants, and if, yes, any possibility to have it integrated in
> Rails 6?
>
> Thanks,
> Alessandro
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] [ANN] Rails 5.2.1 has been released!

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 5.2.1 has been released.


## CHANGES since 5.2.0

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Cable 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.1/actioncable/CHANGELOG.md)
* [Action Mailer 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.1/actionmailer/CHANGELOG.md)
* [Action Pack 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.1/actionpack/CHANGELOG.md)
* [Action View 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.1/actionview/CHANGELOG.md)
* [Active Job 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.1/activejob/CHANGELOG.md)
* [Active Model 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.1/activemodel/CHANGELOG.md)
* [Active Record 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.1/activerecord/CHANGELOG.md)
* [Active Storage 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.1/activestorage/CHANGELOG.md)
* [Active Support 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.1/activesupport/CHANGELOG.md)
* [Railties 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.1/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v5.2.0...v5.2.1).

## SHA-256

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-256 hashes.

Here are the checksums for 5.2.1:

```
$ shasum -a 256 *-5.2.1.gem
ce0d3cf1c76afd3a2f8a751542e2ddfe48cf4005d426a09775b944a780ed6d9f 
actioncable-5.2.1.gem
a667ecf76d300a8faebc5125c25ddb4e46d9c96496c206eee7e02a79c8c33640 
actionmailer-5.2.1.gem
8eb8407ad4c836c46285720b05fa7600bec0327fddc3127b43edf2987a4cfba7 
actionpack-5.2.1.gem
ae45abf777e829e31c6d3a66f43ed792a657b91fe9b5f322f1f63e7bb4b4aa37 
actionview-5.2.1.gem
79383a8dad75cf39677a0096109fc9dcf61cfcf1ef39aeddf2347486c03f94d4 
activejob-5.2.1.gem
a45939b9b0e23225d81786519dda2f1ba9f1568012682aa344d8b1e154b77610 
activemodel-5.2.1.gem
ef3c520c782d5e51ee67231d4b6167db0166d4b451d0c835e0577eb89967875d 
activerecord-5.2.1.gem
4ff9bba1a317bfbc5cd9349bb4e00f6e0aff76d237d68a71ad524b92e0c8cc72 
activestorage-5.2.1.gem
829a480f2cf3747b5e94429d983dfb1645a27d506b365642d08ecc3066373e7e 
activesupport-5.2.1.gem
776cfea45140972f1780236748f7cfe72cf95c032056812128433273c366078c rails-5.2.1.gem
1ba71ee5ec7d85567f9984df1dae2eb7e6c8c2855e6b810582719fb5db20c3a7 
railties-5.2.1.gem
```

As always, huge thanks to the many contributors who helped with this release.


Rafael França

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] [ANN] Rails 5.2.1.rc1 has been released!

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 5.2.1.rc1 has been released.

If no regressions are found, expect the final release on Monday, August 6, 2018.
If you find one, please open an [issue on 
GitHub](https://github.com/rails/rails/issues/new)
and mention me (@rafaelfranca) on it, so that we can fix it before the final 
release.

## CHANGES since 5.2.0

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Cable 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.1.rc1/actioncable/CHANGELOG.md)
* [Action Mailer 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.1.rc1/actionmailer/CHANGELOG.md)
* [Action Pack 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.1.rc1/actionpack/CHANGELOG.md)
* [Action View 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.1.rc1/actionview/CHANGELOG.md)
* [Active Job 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.1.rc1/activejob/CHANGELOG.md)
* [Active Model 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.1.rc1/activemodel/CHANGELOG.md)
* [Active Record 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.1.rc1/activerecord/CHANGELOG.md)
* [Active Storage 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.1.rc1/activestorage/CHANGELOG.md)
* [Active Support 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.1.rc1/activesupport/CHANGELOG.md)
* [Railties 
CHANGELOG](https://github.com/rails/rails/blob/v5.2.1.rc1/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v5.2.0...v5.2.1.rc1).

## SHA-256

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-256 hashes.

Here are the checksums for 5.2.1.rc1:

```
$ shasum -a 256 *-5.2.1.rc1.gem
cf26a51b6483ce88c352687207557825b5ce22d45276f7b4f1168ef71275c5bb 
actioncable-5.2.1.rc1.gem
733f8e2aa203ef83c1bcbc0ffa316b9fafeac8ea5c95dbfc41ec4af440fb8466 
actionmailer-5.2.1.rc1.gem
9858e240e67a35fcfed8d87673ec496d3d2bd970d00fd6414d922772bed06460 
actionpack-5.2.1.rc1.gem
cf68f757d8d71aee003889d8fd49a9f44d0ed348cd07a3ab34c953310f785565 
actionview-5.2.1.rc1.gem
ad4575d404c1339c3782ad55976ab40b123e8217fbebfffc579e56f91b7c9bf1 
activejob-5.2.1.rc1.gem
e1ee68dd9a8e659cbc523a1d0972b8fc4344ecab5a85aec7a7280d33a66076a4 
activemodel-5.2.1.rc1.gem
e184d5b709e0e8351fa32485f63353272a41505b1dbf30c6034a60be321804b1 
activerecord-5.2.1.rc1.gem
04b99f581620933447f10e0e9f8964863994962b3c4580e8c0103b9e3bd5ee18 
activestorage-5.2.1.rc1.gem
f19afc75fa8527b850b12c343cd4e94b7d4d81f0de7126b03912db591789e167 
activesupport-5.2.1.rc1.gem
78fbe88491b0a68f9fe68d7dd8594e2bc102c1aed99a5c5e8acca87e2ec914e7 
rails-5.2.1.rc1.gem
a17f0d61e8da7970c19b98f95196d27115be7603a9badfedccd1329b2daffc93 
railties-5.2.1.rc1.gem
```

As always, huge thanks to the many contributors who helped with this release.

Rafael França

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] [Feature] Symbol to_proc coercions: Enumerable#map can take several symbols

[Rafael Mendonça França]

If you think that method would be useful there is no reason why it should be 
Rails specific. Please send a feature request to the Ruby issue tracker here 
https://bugs.ruby-lang.org/.

Rafael França

On May 11, 2018, 13:10 -0400, Alberto Almagro , wrote:
> These days I have been comparing records in my daily job lots of times, which 
> made me think about a better way to retrieve and compare them. When I want to 
> navigate through several relations in a collection I often see myself writing 
> code like the following:
>
> Given orders as a collection of Order:
> > orders.map(&:order_option).map(&:item).map(&:title)
> => ['Foo', 'Bar', 'Baz']
>
> That is, chaining maps with Symbol to Proc coercions one after each other. 
> Sharing my thoughts with my company's architect we came up with the 
> alternative:
> > orders.map { |order| order&.order_option&.item&.title }
>
> But we agreed that the notation was awful and didn't improve what we had 
> before. With this, I proposed what I think it is more like what we would 
> expect Ruby to have. I would like to add a notation similar to the one we can 
> find at Array#dig or Hash#dig in the following manner:
> > orders.map(&:order_option, &:item, &:title)
> The method doesn't necessarily need to be named map or collect, we can agree 
> on a different name for it if you want. Please share your thoughts with me. 
> If you like this, I would be very happy to write a PR to include it in Rails.
>
> Cheers,
> Alberto Almagro
> --
> You received this message because you are subscribed to the Google Groups 
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] Is it a sane idea to add to_an? as an alias to to_a?

[Rafael Mendonça França]

Ruby used to have `exists?` and `exist?`. The former was deprecatted even that 
in some care it is more natual to read.

I’d follow the same rule here. I believe consistence is more important than 
readability in this case. It make code easier to search, since you only need to 
search for `is_a?` and not `is_an?` and it doesn’t introdoce the overhead of 
having to change which method you use when you rename the constant.

Rafael França

On Apr 19, 2018, 15:51 -0400, Artur Martsinkovskyi , 
wrote:
> As far as I am concerned, Rails try to be as clear and readable as possible 
> in the means of DSL practices. They give the developer all tools for his code 
> to be read like English. We even have aliases like "days" and "minutes" to 
> "day" and "minute" to make forms like 5.days to be read more naturally.
> Writing something like "is_a? Integer" doesn't sound really euphonic to my 
> ear and mind. "is_an? Integer" sounds much better.
>
> Is it OK to submit such a pull request as a part of ActiveSupport core 
> extensions?
> --
> You received this message because you are subscribed to the Google Groups 
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] [Feature Request] adding .sample to ActiveRecord

[Rafael Mendonça França]

One of the first things to do is check if this feature would not proposed
before. I think you will see that it was already proposed and rejected.

See
https://github.com/rails/rails/pull/16997

On Wed, Mar 28, 2018 at 1:21 AM Regan Ryan  wrote:

> Hi there,
>
> I've never contributed to Rails before, so if I'm doing something wrong,
> please point me in the right direction.
>
> I often do something like `User.all.sample` in Rails console to get a
> random record. This is ok, but it loads every record from the db before
> calling `sample` to get a single record. Some projects have 100k+ users, so
> that takes some time.
>
> *I would like to contribute to Rails by adding a
> `ActiveRecord::Scoping::Named::ClassMethods#sample` method to retrieve a
> single (or more if an argument is specified) random record from the db.*
>
> I've been reading a couple of "how to contribute to rails" guides, one of
> them led me to this group. Is anyone able to guide me from here? How do I
> get approval for this feature?
>
> Cheers,
> Regan
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] Adding the ability to show causes in the DebugExceptions view

[Rafael Mendonça França]

Looks good to me. Please open a pr
On Thu, Mar 8, 2018 at 10:20 PM  wrote:

> Hi all,
>
> The Exception#cause
> 
> method has been added to Ruby 2.1.0 back in 2013. Since then Rails has
> adopted it to replace the #original_exception method in a few classes
> such as the ActiveSupport::Rescuable, and I believe we could take a step
> further to help debug an app in development. One low-hanging fruit that I
> see is to add the ability to show causes in the DebugExceptions view. I
> have made a proof-of-concept implementation to see if it could be really
> useful. Here is a screenshot of what it looks like:
>
>
> 
>
> The code could be found here:
> https://github.com/rails/rails/compare/master...yuki24:show-cause-on-debug-view
>
> Of course, there is going to be more things to take care of, such as
> implementing more frontend features and updating how a TemplateError (which
> already uses #cause) could be shown, but I wanted to get feedback
> (especially on the visual aspect of the PoC) before I invest more time in
> it.
>
> Let me know what you all think.
>
> Thanks,
> Yuki
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] Rails 5.1.5 has been released

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 5.1.5 has been released.


## CHANGES since 5.1.4

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Cable 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.5/actioncable/CHANGELOG.md)
* [Action Mailer 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.5/actionmailer/CHANGELOG.md)
* [Action Pack 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.5/actionpack/CHANGELOG.md)
* [Action View 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.5/actionview/CHANGELOG.md)
* [Active Job 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.5/activejob/CHANGELOG.md)
* [Active Model 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.5/activemodel/CHANGELOG.md)
* [Active Record 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.5/activerecord/CHANGELOG.md)
* [Active Support 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.5/activesupport/CHANGELOG.md)
* [Railties 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.5/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v5.1.4...v5.1.5).

## SHA-256

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-256 hashes.

Here are the checksums for 5.1.5:

```
$ shasum -a 256 *-5.1.5.gem
877ff84da386dafdd5d8fc5f8fccd2d87be59cbbfdd2dcac378fb3672c3eb554  
actioncable-5.1.5.gem
9c690209cdd6da82ab335db6195f8179afd5e36ed64a70d63a1c78f34d3150e4  
actionmailer-5.1.5.gem
ed592c0b6a729bd5b96daa11b7a9cc9f930c5fd69650184519d3957e0063eeaa  
actionpack-5.1.5.gem
47ac593df4dc8b1e9e80be8118c61dba0046dc53dd470eecdab1af33233bcc95  
actionview-5.1.5.gem
e063e2042173723a5b135efbe9c4c1cd9a0cf49b28047ae8ef7113b8fc43ecef  
activejob-5.1.5.gem
51d8682d96c14adc5b9064b8c8ed544e4de8bfe69845d80464c2e78a61fe  
activemodel-5.1.5.gem
fc11c06b9cd40b9871c6a82d6497bb0755991846fb3712a1433ee5ad23fc3572  
activerecord-5.1.5.gem
d9b548c63c547b8d6b4c98ca6f8a61d21833ea33a09e7a2295156344d2996c5a  
activesupport-5.1.5.gem
fee9771fc53f3060875267a6789aea9e35975e5c344ff5c3175e27be92a01561  
rails-5.1.5.gem
fa9747717cc279d4dce56a7a75a230dfce8f166a5be120bc2f2f38b91925aa43  
railties-5.1.5.gem
```

As always, huge thanks to the many contributors who helped with this release.

Rafael França

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] [ANN] Rails 5.1.5.rc1 has been released!

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 5.1.5.rc1 has been released.

If no regressions are found, expect the final release on Tuesday, February 6, 
2018.
If you find one, please open an [issue on 
GitHub](https://github.com/rails/rails/issues/new)
and mention me (@rafaelfranca) on it, so that we can fix it before the final 
release.

## CHANGES since 5.1.4

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Cable 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.5.rc1/actioncable/CHANGELOG.md)
* [Action Mailer 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.5.rc1/actionmailer/CHANGELOG.md)
* [Action Pack 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.5.rc1/actionpack/CHANGELOG.md)
* [Action View 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.5.rc1/actionview/CHANGELOG.md)
* [Active Job 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.5.rc1/activejob/CHANGELOG.md)
* [Active Model 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.5.rc1/activemodel/CHANGELOG.md)
* [Active Record 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.5.rc1/activerecord/CHANGELOG.md)
* [Active Support 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.5.rc1/activesupport/CHANGELOG.md)
* [Railties 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.5.rc1/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v5.1.4...v5.1.5.rc1).

## SHA-256

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-256 hashes.

Here are the checksums for 5.1.5.rc1:

```
$ shasum -a 256 *-5.1.5.rc1.gem
3efbb4f001a97abce94694a09ebd9108277d1978b6b7290a2bfb431c121021de  
actioncable-5.1.5.rc1.gem
7b06628240fc5fee17a56b8d50ecc47469c6be54f3e25cdbd46aa79a0f8f0bc6  
actionmailer-5.1.5.rc1.gem
70c6b43e55bad35fc1977fa33b3ec56ab630996befa7cfcb350865fadb9a588a  
actionpack-5.1.5.rc1.gem
a88146826ae7753cf50607fe56dfeff7cf80de88a3e6fbf54102365f666ab0d8  
actionview-5.1.5.rc1.gem
66ec7a29c5b36f30027a752d0e6c1960c0e22da7a4a1fa81fb122c068fe1dd7d  
activejob-5.1.5.rc1.gem
6156e7530215cc9c1aff5a9fa08f587fe014c9fed07f03e7ef159233b5460e4c  
activemodel-5.1.5.rc1.gem
2cc375e96454fc3222e620f3183482365baa1c8d9da7f905dde7c86d9b1c5132  
activerecord-5.1.5.rc1.gem
f451182d63ba5f1229f91d5e96c4eaf31be1261509576d0a3c6118a275472cb4  
activesupport-5.1.5.rc1.gem
aab580fb652a277b9b3801cecd8d93735de02ca650481bf34cef71de6f51f064  
rails-5.1.5.rc1.gem
0a42aaed4a53a4f503358c26e797e6593fbf02ec20537205f9f75818e81ea0c5  
railties-5.1.5.rc1.gem
```

As always, huge thanks to the many contributors who helped with this release.


Rafael França

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] Payload names for 'sql.active_record' instrumentation

[Rafael Mendonça França]

Please do investigate, maybe there is no reason for that difference and we
would be really happy to merge a fix for this.
On Wed, Sep 13, 2017 at 5:57 PM Jeremy Green 
wrote:

> When I subscribe to sql.active_record, when a Post is loaded the payload
> name is "Post Load", which is great and seems to set a pattern on payload
> naming. Following that pattern:
>
>- When a Post is created I would expect the payload name to be "Post
>Create" (or something similar).
>- When a Post is updated I would expect the payload name to be "Post
>Update" (or something similar).
>- When a Post is deleted I would expect the payload name to be "Post
>Delete" (or something similar).
>
> Actual behavior is:
>
>
>- When a Post is created the payload name is "SQL".
>- When a Post is updated the payload name is "SQL".
>- When a Post is deleted the payload name is "SQL".
>
> Is there a reason for the difference? If not, would a patch to fix this be
> considered for merging?
>
> Cheers,
> Jeremy
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] Rails 5.1.2 has been released

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 5.1.2 has been released.

## CHANGES since 5.1.1

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Cable 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.2/actioncable/CHANGELOG.md)
* [Action Mailer 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.2/actionmailer/CHANGELOG.md)
* [Action Pack 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.2/actionpack/CHANGELOG.md)
* [Action View 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.2/actionview/CHANGELOG.md)
* [Active Job 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.2/activejob/CHANGELOG.md)
* [Active Model 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.2/activemodel/CHANGELOG.md)
* [Active Record 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.2/activerecord/CHANGELOG.md)
* [Active Support 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.2/activesupport/CHANGELOG.md)
* [Railties 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.2/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v5.1.1...v5.1.2).

## SHA-256

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-256 hashes.

Here are the checksums for 5.1.2:

```
$ shasum -a 256 *-5.1.2.gem
27943a2642cd94478a88d4e239bb1467476d2acd10f0f588b220e05367163524  
actioncable-5.1.2.gem
e62c4e1b09565e8188d405eac974db1cf31b552064fa9e15fac686556837909f  
actionmailer-5.1.2.gem
b63833831efcfc5fce72deb5bfc14feb7bbe87dd065d8de5904db6dfbc115bca  
actionpack-5.1.2.gem
82efdca96308476cb644d65bc9842167099ed1210ce3c8b626be9ebdcc8c311e  
actionview-5.1.2.gem
d6f762971dfaa312d5f9262eb65eef1c16080cde4790e0e3fd29a0c9651659c4  
activejob-5.1.2.gem
e5d8ae2826f733220dd29792bda5c57d7aa5f6bca036abc1a5fcd4632628f1ce  
activemodel-5.1.2.gem
a3757003b09ac6926d18b32106927d341f906fdf71aa8fa2e3a8e8e0716548ce  
activerecord-5.1.2.gem
0ecf4132689fc06c888c8a1d6678dc22ab972ff5abe797c4fc685582c9ce9d17  
activesupport-5.1.2.gem
4ee8ea1a2760cafbd70fbc878fd0c4ad2fec105082719c818934b39fd4ff0e9b  
rails-5.1.2.gem
db82fbd1dd000b9f5558bfa20c341ccf74ea43716f96e3839be5c219fffe78fc  
railties-5.1.2.gem

```

As always, huge thanks to the many contributors who helped with this release.


-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] Rails 4.2.9 has been released

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 4.2.9 has been released.

Following our [maintenance 
policy](http://guides.rubyonrails.org/maintenance_policy.html),
since the release of Rails 5.1.0, the 4.2 series will only receive new releases 
in case of severe security issues.

## CHANGES since 4.2.8

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer 
CHANGELOG](https://github.com/rails/rails/blob/v4.2.9/actionmailer/CHANGELOG.md)
* [Action Pack 
CHANGELOG](https://github.com/rails/rails/blob/v4.2.9/actionpack/CHANGELOG.md)
* [Action View 
CHANGELOG](https://github.com/rails/rails/blob/v4.2.9/actionview/CHANGELOG.md)
* [Active Job 
CHANGELOG](https://github.com/rails/rails/blob/v4.2.9/activejob/CHANGELOG.md)
* [Active Model 
CHANGELOG](https://github.com/rails/rails/blob/v4.2.9/activemodel/CHANGELOG.md)
* [Active Record 
CHANGELOG](https://github.com/rails/rails/blob/v4.2.9/activerecord/CHANGELOG.md)
* [Active Support 
CHANGELOG](https://github.com/rails/rails/blob/v4.2.9/activesupport/CHANGELOG.md)
* [Railties 
CHANGELOG](https://github.com/rails/rails/blob/v4.2.9/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.2.8...v4.2.9).

## SHA-256

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-256 hashes.

Here are the checksums for 4.2.9:

```
$ shasum -a 256 *-4.2.9.gem
bffbd5830a26af64d92548a831624a5422c77d97b2115c08b668fcbcc26f34ad  
actionmailer-4.2.9.gem
8471fb1f9cc4962f3e000325821f1de0538a12cb580b0772ff9f89fbc8c1f9cd  
actionpack-4.2.9.gem
d7fbbe069f74a6e7ce76cf91d0fede1593a0ed0db875f4630d8343551fb96f12  
actionview-4.2.9.gem
a0086b19823d056efc1c8e7052d6684f54bebe7c9101ba69bd1a58c33d737451  
activejob-4.2.9.gem
dbcd32a5e6294323b893565c0c334f6d89bb92d5085ce5e3d0454de0ed8eb5e3  
activemodel-4.2.9.gem
0be77a1f77b2c8ae0e767c6fafb4c8fdda89c0be49ded0ae6f9644e81a4827a2  
activerecord-4.2.9.gem
5717d2fe6409d4df72f0d20e46d7261503ccafc80ab228e91455d47185190ab4  
activesupport-4.2.9.gem
eaaa4c1cafb3f9bd9f8dd58dd142522e398a5ad0d03abf2e3de364a63d4b7d1a  
rails-4.2.9.gem
ad7b7765849a9aff0c42674f9512c39c098af63bb8476a4076a252fac3b4b2bc  
railties-4.2.9.gem

```

As always, huge thanks to the many contributors who helped with this release.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] Rails 5.1.2.rc1 has been released

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 5.1.2.rc1 has been released.

If no regressions are found, expect the final release on Monday, June 26, 2017.
If you find one, please open an [issue on 
GitHub](https://github.com/rails/rails/issues/new)
and mention me (@rafaelfranca) on it, so that we can fix it before the final 
release.

## CHANGES since 5.1.1

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Cable 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.2.rc1/actioncable/CHANGELOG.md)
* [Action Mailer 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.2.rc1/actionmailer/CHANGELOG.md)
* [Action Pack 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.2.rc1/actionpack/CHANGELOG.md)
* [Action View 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.2.rc1/actionview/CHANGELOG.md)
* [Active Job 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.2.rc1/activejob/CHANGELOG.md)
* [Active Model 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.2.rc1/activemodel/CHANGELOG.md)
* [Active Record 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.2.rc1/activerecord/CHANGELOG.md)
* [Active Support 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.2.rc1/activesupport/CHANGELOG.md)
* [Railties 
CHANGELOG](https://github.com/rails/rails/blob/v5.1.2.rc1/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v5.1.1...v5.1.2.rc1).

## SHA-256

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-256 hashes.

Here are the checksums for 5.1.2.rc1:

```
$ shasum -a 256 *-5.1.2.rc1.gem
ae90de7d8f5d1129a162e9419b65e08870a433ed4eb067bcd44be161de394773  
actioncable-5.1.2.rc1.gem
bd7b3ac7dacb1a983bf2b5dcc56255261421285ef9b5cc5d645d416a1ba42378  
actionmailer-5.1.2.rc1.gem
21b097d2ea1009eaad2487b4461f20a2c76d2ea9786e2fb37dd1e87116ca3621  
actionpack-5.1.2.rc1.gem
689d6580dbef9c81e43fc77185a7916ef7ca2a3d863300f6e47d8199e4bdbd1c  
actionview-5.1.2.rc1.gem
dfa1afc5d701241e25282c318738a8c379fdbd9cf682725f87e1c16584bf3be6  
activejob-5.1.2.rc1.gem
040c3aaa4bf7686efa0e716dc4cf077d4d5b1ef598c81f7d32e86f1f8f26817a  
activemodel-5.1.2.rc1.gem
8bc8b1677051975083717c65a3ee3df612b5e9d381db9d90dc71f3484f514a0b  
activerecord-5.1.2.rc1.gem
69aab1c234f1223ceedb62168df071bdb3483a00be5e186278983eb1ed636e69  
activesupport-5.1.2.rc1.gem
50a14c6e4952297f0a9a510b268ea845833474dccbe1619594c0406ceab5c7fa  
rails-5.1.2.rc1.gem
7c18b3a185f73740b020ecf9414ea8d5c254edddefce64e7383bd137c7626d45  
railties-5.1.2.rc1.gem

```

As always, huge thanks to the many contributors who helped with this release.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] Rails 4.2.9.rc2 has been released!

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 4.2.9.rc2 has been released.

This is going to be the last bug fix release of the 4.2 series, so please test 
this release candidate.

If no regressions are found, expect the final release on Monday, June 26, 2017.
If you find one, please open an [issue on 
GitHub](https://github.com/rails/rails/issues/new)
and mention me (@rafaelfranca) on it, so that we can fix it before the final 
release.

## CHANGES since 4.2.8

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer 
CHANGELOG](https://github.com/rails/rails/blob/v4.2.9.rc2/actionmailer/CHANGELOG.md)
* [Action Pack 
CHANGELOG](https://github.com/rails/rails/blob/v4.2.9.rc2/actionpack/CHANGELOG.md)
* [Action View 
CHANGELOG](https://github.com/rails/rails/blob/v4.2.9.rc2/actionview/CHANGELOG.md)
* [Active Job 
CHANGELOG](https://github.com/rails/rails/blob/v4.2.9.rc2/activejob/CHANGELOG.md)
* [Active Model 
CHANGELOG](https://github.com/rails/rails/blob/v4.2.9.rc2/activemodel/CHANGELOG.md)
* [Active Record 
CHANGELOG](https://github.com/rails/rails/blob/v4.2.9.rc2/activerecord/CHANGELOG.md)
* [Active Support 
CHANGELOG](https://github.com/rails/rails/blob/v4.2.9.rc2/activesupport/CHANGELOG.md)
* [Railties 
CHANGELOG](https://github.com/rails/rails/blob/v4.2.9.rc2/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.2.8...v4.2.9.rc2).

## SHA-256

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-256 hashes.

Here are the checksums for 4.2.9.rc2:

```
$ shasum -a 256 *-4.2.9.rc2.gem
72037af7844a5b7c9da34d8f177ea5ddc02cc50746cf0f7a2423d9fdaf8daf79  
actionmailer-4.2.9.rc2.gem
025ce2b5480da4ead138318256f525b233869f5d63532ab5eb9129da54ea  
actionpack-4.2.9.rc2.gem
d000f1f891b3744000ae73bae8adfe97488b5cfb83929be0e02585e8ef5354bf  
actionview-4.2.9.rc2.gem
5e894159ca0fdab9c1ff34626380431c84b1bd080132019ba3c9a42e2bf7ff97  
activejob-4.2.9.rc2.gem
33d44145becef028f8d241c800cd049e9e015c4b2aca30b68f4eff1d8095  
activemodel-4.2.9.rc2.gem
bdc035ad3ac9687af6897e532aae7b7a3111f7a6bf88444bd20746a1e3633970  
activerecord-4.2.9.rc2.gem
c548e36f68ed575394559951de7d798a6e5d2da1c48a489ac40032ae3b667327  
activesupport-4.2.9.rc2.gem
eb7cdb1b7bb1196ff40d74a98ec44d4521fe3c4e0f4226c814be41e8b1f17d6b  
rails-4.2.9.rc2.gem
b939bbf06be8eb7b8a21fdb64c010a96aa4d23d9346f92b1a105f14bc994c112  
railties-4.2.9.rc2.gem

```

As always, huge thanks to the many contributors who helped with this release.


-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] Rails 5.0.4 has been released

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 5.0.4 has been released.

## CHANGES since 5.0.3

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Cable 
CHANGELOG](https://github.com/rails/rails/blob/v5.0.4/actioncable/CHANGELOG.md)
* [Action Mailer 
CHANGELOG](https://github.com/rails/rails/blob/v5.0.4/actionmailer/CHANGELOG.md)
* [Action Pack 
CHANGELOG](https://github.com/rails/rails/blob/v5.0.4/actionpack/CHANGELOG.md)
* [Action View 
CHANGELOG](https://github.com/rails/rails/blob/v5.0.4/actionview/CHANGELOG.md)
* [Active Job 
CHANGELOG](https://github.com/rails/rails/blob/v5.0.4/activejob/CHANGELOG.md)
* [Active Model 
CHANGELOG](https://github.com/rails/rails/blob/v5.0.4/activemodel/CHANGELOG.md)
* [Active Record 
CHANGELOG](https://github.com/rails/rails/blob/v5.0.4/activerecord/CHANGELOG.md)
* [Active Support 
CHANGELOG](https://github.com/rails/rails/blob/v5.0.4/activesupport/CHANGELOG.md)
* [Railties 
CHANGELOG](https://github.com/rails/rails/blob/v5.0.4/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v5.0.3...v5.0.4).

## SHA-256

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-256 hashes.

Here are the checksums for 5.0.4:

```
$ shasum -a 256 *-5.0.4.gem
f296d82b6494bc6591963f2cd91a08f6853f3ce9b784ab8a6bada5588ceee280  
actioncable-5.0.4.gem
31cb0ca3654c4b9423480fd5b43dec6740c3c234195b50c9906745587ed8c6cc  
actionmailer-5.0.4.gem
22e48ed14a49ef76278fa249035aaf2fb1d8a9abc649444a2510a94ffba3d7e3  
actionpack-5.0.4.gem
f5b53d280c894afd423be26ffc7546266fd6490c91f7e0e3c2dd6524d8d3dbcb  
actionview-5.0.4.gem
65997364e723bf8b041172cb5562da08181d45bbed8d04d9516dc8b6672e1d7f  
activejob-5.0.4.gem
6145ae036d43b5b19c91c1d8c8936d06b475f17bf8a255919ce4afb6015d7216  
activemodel-5.0.4.gem
d82ba1b3519e50c509e0da488f224e5a6164633ebd3c00053e55ade49a8a3d6b  
activerecord-5.0.4.gem
ec3af21ed8df9fdd20d9b9c9a8bef3fc3b7d8b69bcb15a7dbdf8f37072bf2c23  
activesupport-5.0.4.gem
956e9bd0acf86701b139432eb3c9e6bc6d2f51e7cccec9a5dcf9c7d3cb14d87d  
rails-5.0.4.gem
534fbe66df5f7a8c4e2926e7497a7b876f1d34e33b56238db29faf159ad778dc  
railties-5.0.4.gem

```

As always, huge thanks to the many contributors who helped with this release.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] [ANN] Rails 5.0.4.rc1 has been released

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 5.0.4.rc1 has been released.

If no regressions are found, expect the final release on Monday, June 19, 2017.
If you find one, please open an [issue on 
GitHub](https://github.com/rails/rails/issues/new)
and mention me (@rafaelfranca) on it, so that we can fix it before the final 
release.

## CHANGES since 5.0.3

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Cable 
CHANGELOG](https://github.com/rails/rails/blob/v5.0.4.rc1/actioncable/CHANGELOG.md)
* [Action Mailer 
CHANGELOG](https://github.com/rails/rails/blob/v5.0.4.rc1/actionmailer/CHANGELOG.md)
* [Action Pack 
CHANGELOG](https://github.com/rails/rails/blob/v5.0.4.rc1/actionpack/CHANGELOG.md)
* [Action View 
CHANGELOG](https://github.com/rails/rails/blob/v5.0.4.rc1/actionview/CHANGELOG.md)
* [Active Job 
CHANGELOG](https://github.com/rails/rails/blob/v5.0.4.rc1/activejob/CHANGELOG.md)
* [Active Model 
CHANGELOG](https://github.com/rails/rails/blob/v5.0.4.rc1/activemodel/CHANGELOG.md)
* [Active Record 
CHANGELOG](https://github.com/rails/rails/blob/v5.0.4.rc1/activerecord/CHANGELOG.md)
* [Active Support 
CHANGELOG](https://github.com/rails/rails/blob/v5.0.4.rc1/activesupport/CHANGELOG.md)
* [Railties 
CHANGELOG](https://github.com/rails/rails/blob/v5.0.4.rc1/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v5.0.3...v5.0.4.rc1).

## SHA-256

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-256 hashes.

Here are the checksums for 5.0.4.rc1:

```
$ shasum -a 256 *-5.0.4.rc1.gem
c99354a6392225b29f01f2c0c73d27cd641a247298871640032d1e6d9f58  
actioncable-5.0.4.rc1.gem
07698e6e34e4d4c848cf6b13eac7fa7904c8b6bc2583c9675e19ba91fda8  
actionmailer-5.0.4.rc1.gem
828705ee694b5818ec06f05405223ce2f396aa23156e1084a02f0fac9ded2d9d  
actionpack-5.0.4.rc1.gem
c8f07e7f26dd86467be877e17f637b76770ee571dd858e037995754ae38dbcd7  
actionview-5.0.4.rc1.gem
6cf499ce3625be2f9ef8d998885651cee88335767311b6652bca3f1c271161a9  
activejob-5.0.4.rc1.gem
147ec420d4e88fec7b10edb2efb404c563b0551230fc5e930f5c9fe627520c81  
activemodel-5.0.4.rc1.gem
bc8f9aa699f31e5642a14afc3566f6744ad93ac80454306cba986ad530923c08  
activerecord-5.0.4.rc1.gem
95fa2d6d89dec776faabc2878eb6334884455ff6836daaceaf2e7de3f3f07c64  
activesupport-5.0.4.rc1.gem
44843943d4fc377d589bbead59fb74b5bb82e2ab9d1c160fe8884cac6bc17c17  
rails-5.0.4.rc1.gem
95785e5e333e2db554e10e733069db1a3cd0d3137f63ec180491082c8b8afa71  
railties-5.0.4.rc1.gem

```

As always, huge thanks to the many contributors who helped with this release.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] [ANN] Rails 4.2.9.rc1 has been released!

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 4.2.9.rc1 has been released.

If no regressions are found, expect the final release on Monday, June 19, 2017.
If you find one, please open an [issue on 
GitHub](https://github.com/rails/rails/issues/new)
and mention me (@rafaelfranca) on it, so that we can fix it before the final 
release.

## CHANGES since 4.2.8

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer 
CHANGELOG](https://github.com/rails/rails/blob/v4.2.9.rc1/actionmailer/CHANGELOG.md)
* [Action Pack 
CHANGELOG](https://github.com/rails/rails/blob/v4.2.9.rc1/actionpack/CHANGELOG.md)
* [Action View 
CHANGELOG](https://github.com/rails/rails/blob/v4.2.9.rc1/actionview/CHANGELOG.md)
* [Active Job 
CHANGELOG](https://github.com/rails/rails/blob/v4.2.9.rc1/activejob/CHANGELOG.md)
* [Active Model 
CHANGELOG](https://github.com/rails/rails/blob/v4.2.9.rc1/activemodel/CHANGELOG.md)
* [Active Record 
CHANGELOG](https://github.com/rails/rails/blob/v4.2.9.rc1/activerecord/CHANGELOG.md)
* [Active Support 
CHANGELOG](https://github.com/rails/rails/blob/v4.2.9.rc1/activesupport/CHANGELOG.md)
* [Railties 
CHANGELOG](https://github.com/rails/rails/blob/v4.2.9.rc1/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.2.8...v4.2.9.rc1).

## SHA-256

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-256 hashes.

Here are the checksums for 4.2.9.rc1:

```
$ shasum -a 256 *-4.2.9.rc1.gem
f989619bd008bb131ac51c9523a67cf07b04fd02ccbb6a4c862a7e91399abf29  
actionmailer-4.2.9.rc1.gem
ce36a4c32d738bdf0f225c427ed7e31c2e681004fa827f7bbe0c4bd05fb6b264  
actionpack-4.2.9.rc1.gem
e815d4d9ee866145cf9ae78716fed8453a12eace055f4fbd80ae7f4b74e08d27  
actionview-4.2.9.rc1.gem
b03d68ecc055160bc903055649bb47b57de09b68749bd6e40e2e4378cd9a3ce7  
activejob-4.2.9.rc1.gem
734e28fff15f3319be32b6e3cba40519e7c730c88ba49f0b334eb1d63f32c872  
activemodel-4.2.9.rc1.gem
a2f25b8132cca325bf855d7e45c809a122282d8e65f3d6580e40da624c71996a  
activerecord-4.2.9.rc1.gem
7b3b69479110a64f50ac53681f076b5ec21a073b1120c9d7ab201eec0af09d12  
activesupport-4.2.9.rc1.gem
c7de4f0e62498acf407928a5f147a9e297a63e900882f627489e91b033026b69  
rails-4.2.9.rc1.gem
425e43203b35fa28dd9708848c4aaa11706c53fcd75819228a92e6893653f8da  
railties-4.2.9.rc1.gem

```

As always, huge thanks to the many contributors who helped with this release.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] Question about rc1 in RAILS_VERSION file?

[Rafael Mendonça França]

It needs to be 5.2.0.alpha. We are working on this change.

On Mon, Mar 20, 2017 at 9:23 PM Al  wrote:

> Just saw rc1 for Rails. Have a question.
>
> Does https://github.com/rails/rails/blob/master/RAILS_VERSION in master
> (edge rails) need to be "5.1.0.rc1"?
>
> Thanks
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] [ANN] Rails 5.0.2 has been released!

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 5.0.2 has been released.

## CHANGES since 5.0.1

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Cable CHANGELOG](
https://github.com/rails/rails/blob/v5.0.2/actioncable/CHANGELOG.md)
* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v5.0.2/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v5.0.2/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v5.0.2/actionview/CHANGELOG.md)
* [Active Job CHANGELOG](
https://github.com/rails/rails/blob/v5.0.2/activejob/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v5.0.2/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v5.0.2/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v5.0.2/activesupport/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v5.0.2/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v5.0.1...v5.0.2).

## SHA-256

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-256 hashes.

Here are the checksums for 5.0.2:

```
$ shasum -a 256 *-5.0.2.gem
bec943d44cc3c91b1be7ed9dd0a750e89668035089905f8b357eafb7019402e0
 actioncable-5.0.2.gem
4b1d4e08d911a410c6ef0314ca897a1e73abb8757707cc9f0766edc6a4c47e92
 actionmailer-5.0.2.gem
9761c35da0cd2c2057fab74c2b4f27a748deb8e848c8db1eed0a078c43a31bce
 actionpack-5.0.2.gem
002b3c3b858b0748a73ebcb6f8fcdec24b5ccda948646261530ff028ded43365
 actionview-5.0.2.gem
6da5f44958fc83f8c10dfa03d22b067ffc3b1032e3a881a282d786396ded00bc
 activejob-5.0.2.gem
9c927aa343b7e32ea87a8d7cf9acde0291de219af86d7ed38ae4733d8a19c06c
 activemodel-5.0.2.gem
6070757a7816b6676568a7d6c6e160ae8cd9a1b93f45fe3ce03d21f35c3accc7
 activerecord-5.0.2.gem
e02921c1a516af2f6ab492af483e0c6aab113b9535a3fd86e901efaa843b72b5
 activesupport-5.0.2.gem
49c6c350286e2f177df5c2214f9668f0866d87411ab5a63e051e25eb64453f70
 rails-5.0.2.gem
45f7a574e8f1c6dcc6c91ed6c6f42894b3d8abc132f4a5cff0148e6a18fa8d5a
 railties-5.0.2.gem

```

As always, huge thanks to the many contributors who helped with this
release.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] [ANN] Rails 5.0.2.rc1 has been released!

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 5.0.2.rc1 has been released.

If no regressions are found, expect the final release on Wednesday, March
1, 2017.
If you find one, please open an [issue on GitHub](
https://github.com/rails/rails/issues/new)
and mention me (@rafaelfranca) on it, so that we can fix it before the
final release.

## CHANGES since 5.0.1

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Cable CHANGELOG](
https://github.com/rails/rails/blob/v5.0.2.rc1/actioncable/CHANGELOG.md)
* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v5.0.2.rc1/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v5.0.2.rc1/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v5.0.2.rc1/actionview/CHANGELOG.md)
* [Active Job CHANGELOG](
https://github.com/rails/rails/blob/v5.0.2.rc1/activejob/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v5.0.2.rc1/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v5.0.2.rc1/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v5.0.2.rc1/activesupport/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v5.0.2.rc1/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v5.0.1...v5.0.2.rc1).

## SHA-1

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-256 hashes.

Here are the checksums for 5.0.2.rc1:

```
$ shasum -a 256 *-5.0.2.rc1.gem
89e447f43e924c465d4bc19efe333e67966daddb3d163cf6cf9b324578628811
 actioncable-5.0.2.rc1.gem
56621e6cea32533f15ae0abab1c3a385c4f0b92f3eab2f3e6e6a292f41a3d8f4
 actionmailer-5.0.2.rc1.gem
deacc6b0c965d73adf2259fca2d2e81dd27ed81402e742fd6b70210b6970dd0c
 actionpack-5.0.2.rc1.gem
f0e55b9cc876f55dd4d1585a65db8f4b15b3e90ad4e65cc1f3e2dfe893da4460
 actionview-5.0.2.rc1.gem
23ffc888458274eb251b181d9a8457f8aea2ee1307815809c5fa087f016cc2ea
 activejob-5.0.2.rc1.gem
b56723d63d8cb5bea72318162a97c6b9062ced57f784252434a562b964eebeb5
 activemodel-5.0.2.rc1.gem
e5821ea73f6ad65c5f26c236fec5bd443f962b8f6caa22b277fc2654c0cbf137
 activerecord-5.0.2.rc1.gem
e35c127ae13bb87f10ef2e39661586103619e963b9135f66bfa076a9378fa222
 activesupport-5.0.2.rc1.gem
a7e221850b4ba50150d814c12750b559b2bf20c164cad3f647e8c7b41da267ed
 rails-5.0.2.rc1.gem
e14777d86c544f7c368f02b8e6d805cdc3bd62c40245ddb4c0f438220437e73a
 railties-5.0.2.rc1.gem

```

As always, huge thanks to the many contributors who helped with this
release.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] Regarding JavaScript testing

[Rafael Mendonça França]

Thank you for the feedback Rodrigo.

I think it is worth to explore possibilities for JavaScript tests. I don’t
see why Rails could not integrate better with the test ecosystem in the
JavaScript community and I think it is a valuable direction to take. We
didn’t included anything in this line in 5.1 because we didn’t have someone
the champion this feature but we would be happy to have something for a
next release.

So, now that the ground base is set for better relationship with the
JavaScript community it is just a matter of someone willing to explore how
the test history will be.

Looking forward to see what is coming on this front!

On Thu, Feb 23, 2017 at 3:59 PM Rodrigo Rosenfeld Rosas 
wrote:

> Hi, I was happy to read the new features for Rails 5.1 here:
>
> http://weblog.rubyonrails.org/2017/2/23/Rails-5-1-beta1/
>
> Specially as I have already been using webpack,npm and yarn for a while
> (well, yarn just recently, of course) and I'm pretty happy with the
> results. My main motivations were client-side performance improvements
> and source-maps support, but there were many more reasons I chose
> webpack as stated in the Goals section of this article:
>
>
> http://rosenfeld.herokuapp.com/en/articles/2016-02-29-getting-an-spa-to-load-the-fastest-possible-way-and-how-webpack-can-help-you
>
> As you can guess, I'm pretty happy with the direction Rails is taking as
> an opinionated system (even though I'm moving towards a discrete system
> I still see value in frameworks like Rails that are full featured and
> opinionated, specially for new or small-sized applications).
>
> There's just one thing I found missing in this release notes and I don't
> want to sound critical. It's the other way around. As I said, I'm pretty
> happy with the direction Rails is taking, so this is a suggestion to
> improve it further if someone is interested on working or discussing
> this topic. I don't have time for that so if anyone is interested on
> making it happen feel free to disregard this suggestion.
>
> I've been writing Single Page Applications since 2009 and even though
> I've tried testing them through solutions such as Capybara (and similar
> solutions for other languages such as Selenium) it doesn't really scale.
> At some point I completely dropped Capybara because I found that those
> specs were hardly executed since they were disabled by default because
> they were simply too slow.
>
> I'm not saying adding Capybara to Rails was a bad idea. I do see value
> in it and I'm happy Rails adds it by default. I'm just saying that I
> feel like Rails isn't really aware of how SPA applications are developed
> in the wide. While browser tests allow you to test JavaScript they are
> not the only way. Using JavaScript test frameworks is what actually
> enable SPA testing to succeed. Since Rails 5.1 is supporting SPA I think
> it would be awesome if it also integrated some testing framework, maybe
> on top of Karma.js, for fulfilling that purpose and stablishing good
> practices just like it does for Ruby code.
>
> https://karma-runner.github.io/1.0/index.html
>
> Karma already exists for a while and looks like a mature solution to me,
> and could be integrated to several JavaScript frameworks, and tests can
> be run from the console, making it easier to integrate to CIs. Maybe
> Rails could adopt some well known framework such as Jasmine or Mocha for
> creating the stubs for new JS files.
>
> Well, this is just an idea. I use my own JS test framework in our
> application, that's why I don't have a strong opinion on those test
> runners mentioned above, but I had some experience with them and they
> should be good enough for most applications.
>
> Once again, thanks a lot for this 5.1 release. It seems like Rails is
> getting exciting again :)
>
> Best,
>
> Rodrigo.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] [ANN] Rails 4.2.8.rc1 has been released!

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 4.2.8.rc1 has been released.

If no regressions are found, expect the final release on Wednesday,
February 15, 2017.
If you find one, please open an [issue on GitHub](
https://github.com/rails/rails/issues/new)
and mention me (@rafaelfranca) on it, so that we can fix it before the
final release.

## CHANGES since 4.2.7.1

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.2.8.rc1/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.2.8.rc1/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v4.2.8.rc1/actionview/CHANGELOG.md)
* [Active Job CHANGELOG](
https://github.com/rails/rails/blob/v4.2.8.rc1/activejob/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.2.8.rc1/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.2.8.rc1/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.2.8.rc1/activesupport/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.2.8.rc1/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.2.7.1...v4.2.8.rc1).

## SHA-1

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-1 hashes.

Here are the checksums for 4.2.8.rc1:

```
$ shasum *-4.2.8.rc1.gem
cb6ffe33124a95c84598437c3698f016acc30b01  actionmailer-4.2.8.rc1.gem
ed4c50bf4418ec6b82bf17cf41fcd8dd28a4c423  actionpack-4.2.8.rc1.gem
7ccc80e22af39350f0f2d8055663d1adb2320caa  actionview-4.2.8.rc1.gem
7dc4923abcbf3587c5aa6d6cf425ad0e3f69877e  activejob-4.2.8.rc1.gem
b97863c12a06beca60fe0f1e5760fd2e21f0d40d  activemodel-4.2.8.rc1.gem
40e7d2c780f8b0e70adb2a725fb773648539b4fe  activerecord-4.2.8.rc1.gem
edc12197ae5d6e13d6618c40143196ddd5debadd  activesupport-4.2.8.rc1.gem
04849eea3d5c5f20aa51b6dbd31357c9328d10ab  rails-4.2.8.rc1.gem
e05dce3a6c14b36b35bf1ea13433677e867602ae  railties-4.2.8.rc1.gem
```

As always, huge thanks to the many contributors who helped with this
release.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] [Suggestion] Allow proc in belongs_to's optional flag

[Rafael Mendonça França]

I believe this make `belongs_to` too complex and open a precedent to people
want to customize the validation in other ways using the `belongs_to`
syntax. The required validation is just a convenience. It is a good default
but sometimes people want more than the default. In those cases they should
be explicitly defining their own validation as your example.

On Mon, Feb 6, 2017 at 9:51 PM Lucas Caton  wrote:

> Hi all,
>
> Any thoughts on this?
>
> *Lucas Caton*
> @lucascaton  | lucascaton.com.br
>
>
>
> On Wed, 1 Feb 2017 at 18:40 Lucas Caton  wrote:
>
> Hi there,
>
> What about allowing to pass a proc to belongs_to's optional flag?
>
> So instead of the following:
>
> class Transaction < ApplicationRecord
>   belongs_to :category, optional: true
>   validates :category, presence: { message: :required }, if: :auto_created?
> end
>
> We could write:
>
> class Transaction < ApplicationRecord
>   belongs_to :category, optional: ->(record) { record.auto_created? }
> end
>
>
> I'm happy to submit a PR if you agree with the suggestion.
>
> Cheers,
> Lucas.
>
> --
>
> You received this message because you are subscribed to a topic in the
> Google Groups "Ruby on Rails: Core" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/rubyonrails-core/V-padeQT7SQ/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to
> rubyonrails-core+unsubscr...@googlegroups.com.
>
>
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] Unit testing ActionCable

[Rafael Mendonça França]

https://github.com/rails/rails/pull/23211
On Tue, Nov 22, 2016 at 12:55 PM Roman Snitko 
wrote:

> It seems there currently is no easy (or hard even) way to unit test
> ActionCable channels, which makes me very sad. There is a bit of logic in
> my Channels which would be very nice to cover with tests. Ideally, I'd like
> to have something like this:
>
> it "rejects connection if current_user isn't the owner of the
> contract" do
>   channel = create_channel(:contract)
>   sign_in @unauthorized_user
>   expect(channel.subscribe(params: {contract_id: 1}).to
> reject_connection
> end
>
> Is this something even remotely likely to happen? I googled very hard and
> I also checked every ActionCable issue (opened & closed) and couldn't find
> anyone asking this question.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] New i18n release (0.8.0.beta1)

[Rafael Mendonça França]

I ran the Rails test suite with the beta version of i18n and everything is
looking great! https://travis-ci.org/rails/rails/builds/177754824

Thank you for taking care of it Ryan.

On Sun, Nov 20, 2016 at 9:46 PM Ryan Bigg  wrote:

> Hello all,
>
> I've been helping Sven Fuchs maintain the i18n gem and I'm pleased to let
> you know that I'm prepping a new release of this gem (0.8.0). This new
> release will affect every Rails version since Rails 3.2, so I want to make
> sure this release is bullet-proof!
>
> Included in this release are some relatively simple new features and a
> bunch of bug fixes. Info about this release is available at
> https://github.com/svenfuchs/i18n/releases/tag/0.8.0.beta1
>
> We would love it if you could test out this gem in your applications by
> simply adding it to your application's Gemfile:
>
> gem 'i18n', '0.8.0.beta1'
>
> Then run your application's tests and let us know if this gem version bump
> has broken anything. If it has, please post your issue to
> https://github.com/svenfuchs/i18n/issues/new with some steps to
> reproduce. We'll try to attend to this issues in a timely fashion.
>
> Since we're at the end of the year and it's typically a crazy time, the
> final release of 0.8.0 will be done likely in the middle of January. We
> would rather not break things in the middle of December!
>
> Thanks for taking the time to test out this release!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] Link_to conditional classes with 'class:' feature request (and all the other helpers that take CSS classes)

[Rafael Mendonça França]

There is an open question here. From here those conditional methods are
coming from? From helpers modules? This will add a lot of this kind of
methods in the global namespace since helpers are global and will make code
harder to understand.

On Mon, Oct 24, 2016 at 10:12 PM  wrote:

> Heya,
>
> Setting condition classes is a huge pain in rails at the moment, or maybe
> i am missing it but i can't see to find it. borrowed from react components
> kind of style.
>
> I want something like this (the class selected is only added if the value
> is true)
>
> link_to("Homepage", root_path, class: {selected: selected?})
>
> -> a href class="selected" and other
>
> You can do the same thing to add multiple classes too
>
> link_to("Hello", root_path, class: {class: {btn:true, selected: selected?}}
>
> I think this would be awesome, anything reasons why we shouldn't implement
> this?
>
> Cheers,
>
> - Emile
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] [Suggestion] Prevent Rails from writing development/test log files by default

[Rafael Mendonça França]

I personally use `test.log` a lot to check the sql queries that are being
made in my test run.

Also setups using pow or any long running web server only uses the
development.log so changing this will break that setup. I can see we
disabling the boardcast, but I’d not do that by default.

On Mon, Oct 24, 2016 at 11:20 PM Lucas Caton  wrote:

> Hi there.
>
>
> I know this, although easy, would be a big step. So I'd love to hear your
> thoughts.
>
>
> I can't remember the last time I needed to open/read log/development.log
>  or log/test.log.
> This is just consuming disk space unnecessarily (my test.loge easily
> reaches more than 1 GB!).
>
> After talking to some other developers, all of them agreed they don't use
> it as well.
>
>
> What if we change this behaviour to be optional? It'd still display the
> logs through the STDOUT, though.
>
> I've been doing it in my projects and couldn't find a reason not to do it.
>
>
> The way I currently do it is similar to what Heroku's rails_12factor gem
> used to do (and now is the default in Rails for *production* environment):
>
>
> # config/environments/development.rb
>
> # Prevents from writing logs on `log/development.log`
>
> logger   = ActiveSupport::Logger.new(STDOUT)
>
> logger.formatter = config.log_formatter
>
> config.logger= ActiveSupport::TaggedLogging.new(logger)
>
>
> # config/environments/test.rb
>
> # Prevents from writing logs on `log/test.log`
>
> config.log_level = :warn
>
> logger   = ActiveSupport::Logger.new(STDOUT)
>
> logger.formatter = config.log_formatter
>
> config.logger= ActiveSupport::TaggedLogging.new(logger)
>
>
> Thank you,
> Lucas.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] [Feature Request] 'On' option for after_save callbacks

[Rafael Mendonça França]

Is not that what after_update does?
On dom, 4 de set de 2016 at 17:46 Anuj N  wrote:

> Hi folks!
>
> As per https://github.com/rails/rails/issues/22515, 5.0 saw
> after_create_commit, after_update_commit, after_destroy_commit being
> added as aliases to after_commit, on:create, etc. From
> https://github.com/rails/rails/issues/12502, it seems that `on` flag only
> works for after_commit but not after_save.
>
> I was wondering if it would be possible to allow `on` flag for after_save
> as well and see similar aliases if that option is implemented? Often times,
> I have been wanting to trigger those callbacks only on updates and not say
> create, and haven't found a clean solution. It also feels consistent in
> style with the validation callbacks and now after_commit callbacks.
>
> Thank you,
> Anuj
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] Timestamps in migration

[Rafael Mendonça França]

No problem at all. I'm really not sure if the deprecation is there so if it
is not please let us know so we can fix this.

On Tue, Jul 5, 2016 at 4:11 PM Andrey Molchanov <neod...@gmail.com> wrote:

> Thank you, I will be more attentive
>
> вторник, 5 июля 2016 г., 22:08:31 UTC+3 пользователь Rafael Mendonça
> França написал:
>>
>> Yes. And I think in Rails 4.2 it show a deprecation warning to tell
>> people that it is going to default to null: false in Rails 5
>> ​
>>
>> On Tue, Jul 5, 2016 at 4:07 PM Andrey Molchanov <neo...@gmail.com> wrote:
>>
>>> My bad. Yes, it is. But in 4.2.7 it is`n. You specify not add it in 4s
>>> versions?
>>>
>>> вторник, 5 июля 2016 г., 22:00:37 UTC+3 пользователь Rafael Mendonça
>>> França написал:
>>>>
>>>> I think this is already the default in Rails 5. Isn't?
>>>>
>>>> On Tue, Jul 5, 2016 at 3:52 PM Andrey Molchanov <neo...@gmail.com>
>>>> wrote:
>>>>
>>> Hi there!
>>>>> If we create migrate with
>>>>>
>>>>> t.timestamps
>>>>>
>>>>> it will add lines
>>>>>
>>>>> t.datetime "created_at"
>>>>>
>>>>> t.datetime "updated_at"
>>>>>
>>>>> In schema.rb file.
>>>>> What are you think about if *by default* in this case null option
>>>>> will be false without explicitly specifying?
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "Ruby on Rails: Core" group.
>>>>>
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to rubyonrails-co...@googlegroups.com.
>>>>> To post to this group, send email to rubyonra...@googlegroups.com.
>>>>
>>>>
>>>>> Visit this group at https://groups.google.com/group/rubyonrails-core.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Ruby on Rails: Core" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to rubyonrails-co...@googlegroups.com.
>>> To post to this group, send email to rubyonra...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/rubyonrails-core.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] Timestamps in migration

[Rafael Mendonça França]

Yes. And I think in Rails 4.2 it show a deprecation warning to tell people
that it is going to default to null: false in Rails 5
​

On Tue, Jul 5, 2016 at 4:07 PM Andrey Molchanov <neod...@gmail.com> wrote:

> My bad. Yes, it is. But in 4.2.7 it is`n. You specify not add it in 4s
> versions?
>
> вторник, 5 июля 2016 г., 22:00:37 UTC+3 пользователь Rafael Mendonça
> França написал:
>>
>> I think this is already the default in Rails 5. Isn't?
>>
>> On Tue, Jul 5, 2016 at 3:52 PM Andrey Molchanov <neo...@gmail.com> wrote:
>>
> Hi there!
>>> If we create migrate with
>>>
>>> t.timestamps
>>>
>>> it will add lines
>>>
>>> t.datetime "created_at"
>>>
>>> t.datetime "updated_at"
>>>
>>> In schema.rb file.
>>> What are you think about if *by default* in this case null option will
>>> be false without explicitly specifying?
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Ruby on Rails: Core" group.
>>>
>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to rubyonrails-co...@googlegroups.com.
>>> To post to this group, send email to rubyonra...@googlegroups.com.
>>
>>
>>> Visit this group at https://groups.google.com/group/rubyonrails-core.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] Timestamps in migration

[Rafael Mendonça França]

I think this is already the default in Rails 5. Isn't?

On Tue, Jul 5, 2016 at 3:52 PM Andrey Molchanov  wrote:

> Hi there!
> If we create migrate with
>
> t.timestamps
>
> it will add lines
>
> t.datetime "created_at"
>
> t.datetime "updated_at"
>
> In schema.rb file.
> What are you think about if *by default* in this case null option will be
> false without explicitly specifying?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] [ANN] Rails 4.2.7.rc1 and 4.1.16.rc1 have been released!

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 4.2.7.rc1 and 4.1.16.rc1 have been
released.

As [Rails 5 was released](
http://weblog.rubyonrails.org/2016/6/30/Rails-5-0-final/), this is probably
going to be the last release of Rails 4.1. Please take some time to upgrade
your application to
Rails 4.2 or Rails 5.

If no regressions are found expect the final release this Thursday, on July
7, 2016.
If you find one, please open an [issue on GitHub](
https://github.com/rails/rails/issues/new)
and mention me (@rafaelfranca) on it, so that we can fix it before the
final release.

## CHANGES since 4.1.15

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.1.16.rc1/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.1.16.rc1/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v4.1.16.rc1/actionview/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.1.16.rc1/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.1.16.rc1/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.1.16.rc1/activesupport/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.1.16.rc1/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.1.15...v4.1.16.rc1).

## CHANGES since 4.2.6

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.2.7.rc1/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.2.7.rc1/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v4.2.7.rc1/actionview/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.2.7.rc1/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.2.7.rc1/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.2.7.rc1/activesupport/CHANGELOG.md)
* [Active Job CHANGELOG](
https://github.com/rails/rails/blob/v4.2.7.rc1/activejob/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.2.7.rc1/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.2.6...v4.2.7.rc1).

## SHA-1

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-1 hashes.

Here are the checksums for 4.1.16.rc1:

```
$ shasum *4.1.16.rc1.gem*
8e0be05cfb4e4516c75cc12c971fe4924f111762  actionmailer-4.1.16.rc1.gem
1ad0c0c1bc13ddf9f85c6b1d5cd6288d8d0114d6  actionpack-4.1.16.rc1.gem
ee83721f8f7a95b23aa93163fe3e01ba89ca046a  actionview-4.1.16.rc1.gem
35fa99af4f158079a444cb8473a0a3dd0465220b  activemodel-4.1.16.rc1.gem
680a69dc13474894c84054a1f2a9d23868d6000e  activerecord-4.1.16.rc1.gem
a03b6a27496cf08e215db8e487f3a06a45b0e29a  activesupport-4.1.16.rc1.gem
70bf01fb349592a8473d3ffedb873c9f9abc293d  rails-4.1.16.rc1.gem
5c6cc7659065da6f61fc3ff0bcc13439a4df8ee2  railties-4.1.16.rc1.gem
```

Here are the checksums for 4.2.7.rc1:

```
$ shasum *4.2.7.rc1.gem*
6deda04a33d767f0d9d7be5a199c98c359701b34  actionmailer-4.2.7.rc1.gem
723e016bcf59cb860b6343a4936f417c927dab09  actionpack-4.2.7.rc1.gem
19cef0c8418c294ebc46547e29d460c554a4d77c  actionview-4.2.7.rc1.gem
f1038a46fdcbd888dca12285d7bf8db2ea40f80c  activejob-4.2.7.rc1.gem
c48f4b32f0da8ea64541e8ca80b4e15a47e01ad1  activemodel-4.2.7.rc1.gem
0ef45fd5da001370593558cb8b64f5aba6d7de16  activerecord-4.2.7.rc1.gem
5969a35bf853ce9f872f6c99f4d75572d436a4ed  activesupport-4.2.7.rc1.gem
ac23853084ac321ce40a0e79d2f878ad18dac7a3  rails-4.2.7.rc1.gem
e9dde94765e7a8682ff4675f8ae47244a996644d  railties-4.2.7.rc1.gem
```

I'd like to thank you all, every contributor who helped with this release.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] [Feature Request] Force test schema to be up to date when running tests

[Rafael Mendonça França]

Automatic test schema maintainance is a feature of Rails since 4.1
http://guides.rubyonrails.org/4_1_release_notes.html#railties-notable-changes

On Tue, Jun 28, 2016 at 5:32 PM Chad Woolley 
wrote:

> +1, this is one of a few things that doesn't "work out of the box" for
> databases in real-world usage.  I always end up having some version of a
> custom "db:prepare" which does extra necessary things for my apps.
>
> FYI, this thread is somewhat related, in that it's also about confusion
> about the behavior of the 'test' environment (and also unaddressed):
> https://groups.google.com/forum/#!searchin/rubyonrails-core/environment$20agnostic/rubyonrails-core/kqKoJHcQu9U/xx9J2BLOBgAJ
>
> -- Chad
>
> On Tue, Jun 28, 2016 at 11:26 AM, Ryan Jones  > wrote:
>
>> Every so often I'll run a test suite and it will have a large number of
>> failures. After debugging it's normally something as simple as the test
>> schema being out of date. I then run bin/rake db:test:prepare and
>> everything is fine.
>>
>> If I run my development environment and my schema is out of date, it
>> throws an error and forces me to run bin/rake db:migrate. Should we be
>> doing the same thing when we're running tests? Or at the very least maybe
>> throwing a warning that the test schema is 'out of date'?
>>
>> On one of the first apps I was building (a few years ago) I remember
>> spending a few hours tracking down why my test was failing. I was new to
>> 'TDD' and I thought it was something I was doing wrong. I called a friend
>> and he asked 'did you run db:test:prepare?' and that solved my problem. I
>> don't run into this issue as much anymore, but I think it might prevent
>> some frustration by new rails users.
>>
>> I'm trying to think of why we wouldn't be doing this and my mind is
>> coming up blank. Let me know your thoughts!
>>
>> Thanks,
>> Ryan
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Ruby on Rails: Core" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to rubyonrails-core+unsubscr...@googlegroups.com.
>> To post to this group, send email to rubyonrails-core@googlegroups.com.
>> Visit this group at https://groups.google.com/group/rubyonrails-core.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] [Feature request] Raise an error for invalid options on migrations

[Rafael Mendonça França]

It is an limitation of the implementation.

All database adapters share the same migrations helpers. If the SQLite3
adapter doesn't not accept the `limit` option to a string column and we
raise an error when the users pass it the PostgreSQL adapter will also
raise an error even that it is supported for that database.

Today it is also possible to write plugins to the migration helper easily
without having to monkey patch them, changing to raise errors when the
option is unknown will require these plugins to monkey patch them.

On Mon, Jun 13, 2016 at 1:19 PM Ian Ker-Seymer 
wrote:

> Rafael, why would it not be possible? Is this an architectural issue with
> the current rails code?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] [Feature request] Raise an error for invalid options on migrations

[Rafael Mendonça França]

Like I said in the original issue
https://github.com/rails/rails/issues/25330#issuecomment-224787746

This proposed solution makes impossible to different adapters introduce
different options to the migration helpers without monkey patching rails.
In you specific case, a database like Oracle could accept a limit option in
the text column and that would raise an error.



On Thu, Jun 9, 2016 at 2:04 PM Jason Fleetwood-Boldt 
wrote:

> +1 on guardrails for Rails (pun intended)
>
> Silent unseen errors are always the worst kind.
>
> -jason
>
>
> On Jun 8, 2016, at 11:02 PM, Ian Ker-Seymer  wrote:
>
> Currently, when creating a migration and the user specifies an invalid
> option, the migration silently succeeds and does not notifiy the user that
> the option is meaningless.
>
> Given this migration for postgres:
>
> ```ruby
> class CreatePost < ActiveRecord::Migration[5.0]
>   def change
> create_table :posts do |t|
>   t.text :description, limit: 5000
> end
>   end
> end
> ```
>
> When we run this migration, the schema will be created, and everything
> appears to have succeeded. It will result in something like this:
>
> ```ruby
> ActiveRecord::Schema.define(version: 20160601201548) do
>   create_table "posts", force: :cascade do |t|
> t.text "description", null: false
>   end
> end
> ```
>
> The schema is correct and does not impose a `limit: 5000` on the
>  `description` column. However, I find the developer experience to be
> confusing as it does not warn that there is no possible limit constraint on
> a `text` column. This can lead to issues like a developer expecting a limit
> when there is none.
>
>
> *Proposed solution*
>
> Raise an error where there are invalid options given in migrations.
> Instead of silently succeeding on `rake db:migrate`, throw a
> `ActiveRecord::InvalidDatabaseConstaint` or something similar. This way,
> the user is made aware of mistakes they may have made.
>
> I am happy to work on this issue if there is consensus that this is a
> positive change. Please post your thoughts here! Thanks :smile:
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] proposal: add option to pretty-print in json renderer

[Rafael Mendonça França]

In Rails 5.1 you will be able to change how the JSON is serialized. See
https://github.com/rails/rails/pull/21496.

On Mon, May 23, 2016 at 7:59 PM Gabriel Burt 
wrote:

> My reading of the action_controller json renderer
> 
>
> add :json do |json, options|
>>   json = json.to_json(options) unless json.kind_of?(String)
>
>
> is that `options` come from the options hash you pass to `render` -- so,
> it's a hash.  But my reading of Hash#to_json
> 
> is that the only argument it accepts is a JSON::State object, not a hash.
> I think that means you can't do anything useful (like enabling
> pretty-print) by passing options to the action_controller json renderer
> (passing `indent: '  '` doesn't work, for instance).
>
> Given that, I'm proposing changing the :json renderer to something more
> like this:
>
> +config_accessor :default_json_pretty
>> +self.default_json_pretty = false if default_json_pretty.nil?
>> +
>>
>  add :json do |json, options|
>> -  json = json.to_json(options) unless json.kind_of?(String)
>> +  unless json.kind_of?(String)
>> +pretty = false
>> +pretty = options[:pretty] unless options[:pretty].nil?
>> +pretty = default_json_pretty if pretty.nil?
>> +
>> +json = json.to_json(pretty ? JSON::PRETTY_STATE_PROTOTYPE : nil)
>> +  end
>>
>
> This would let you specify an app-wide default for `render json: ..`
> pretty printing, but also let you specify it (and override the default) for
> any given render call (with `render json: .., pretty: false`).  And since
> to_json(options) already seems to be ignoring non-JSON::State arguments, it
> shouldn't hurt to not pass them into it anymore.
>
> Did I miss or missunderstand anything in the above?  Does this sound like
> a good idea that I should work up?
>
> Thanks!
>
> Gabriel
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] Raise on missing translations (unify controllers and views)

[Rafael Mendonça França]

I'm positive to adding such generic option.

I18n already have the `transalate!` method to raise an error if the
translation is missing maybe we should use it in the Rails wrappers?

On Mon, May 23, 2016 at 7:59 PM Kevin Sjöberg  wrote:

> I'm on a mission to unify the logic for raise_on_missing_translation between
> controllers and views. Currently this is scoped to ActionView. I'm
> proposing that we move the config option to the I18n scope, giving us
> config.i18n.raise_on_missing_translations and thus deprecating 
> config.action_view.raise_on_missing_translations.
> We then update AbstractController#translate and
> TranslationHelper#translate to use the new config option and raise errors
> accordingly.
>
> Since I'm not usually contributing to Rails I might overlook some
> technical or architectural aspects of the problem. Would love some feedback
> on the approach I'm taking. If all sounds good, I will begin working on a
> pull request.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] Improve user feedback in rails update [Feature Request]

[Rafael Mendonça França]

Hi,

For what I could see in your explanation you are expecting the update task
to teach people about the changes between some pre-releases. I don't think
it is sustainable to do that. I'm all for improving the update task to give
better feedback when do a minor version upgrade.

I believe we have almost all this information in the upgrading guide, so do
you think that a link to the upgrade guiding after the command finish would
be a good way to improve the process?

On Mon, May 16, 2016 at 1:00 PM Hiren Mistry  wrote:

> Hi,
>
> I would like to present a feature request to the `rails rails:update`
> command. This feature request is about user experience and making
> developers lives better. It goes alongs the same lines as your recent
> migration from `rake` to `rails`, which has been an absolute joy to use,
> much, much more than something that runs a fraction of second faster.
>
> I think it would be really nice if the `rails update` command provided
> more user feedback for files that it does not update. Some examples:
>
>1. if it printed out in STDOUT that I should change the
>data-turbolinks-track from true to reload in my `application.html`
>file because it wasn't able to find the `application.html.erb` file. (I
>used HAML, SASS, and Rspec in my rails app.)
>2. code in `cable.coffee` has changed and needs to be replaced with
>`cable.js`.
>3. mention there has been additions like
>config/initializers/ssl_options.rb and
>config/initializers/to_time_preserves_timezone.rb files, but it's not
>needed for my application because... (post a link to refer to) and that's
>why it did not create them.
>
> Basically with better feedback, we can save all the developers time and
> anxiety when upgrading. With a little feedback like this, dev's know there
> are additional changes that needs to be done that the script wasn't able
> to, or new things/configuration changes with reference links to research so
> they can determine what they wish to do about it. When upgrading becomes
> easier and pleasant, then more dev's will be willing to upgrade quicker
> which results in less support for older versions.
>
> Regards,
> Hiren.
>
> PS - I got this insight from my recent experience updating rails (see issue
> #24983 ).
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] Significant change should be better explained in the Changelog regarding non ERB view partials

[Rafael Mendonça França]

Hi, no worries. I can think in a better wording open a PR and ping you on
it.

Yes, the change is intentional and it is not html safe by default by
definition. The whole idea of this change is to avoid people to rendering
unsafe responses as safe by mistake.

See https://github.com/rails/rails/issues/2394 and
https://github.com/rails/rails/pull/6309 for background.

On Sun, May 8, 2016 at 3:01 PM Rodrigo Rosenfeld Rosas <rr.ro...@gmail.com>
wrote:

> Hi Rafael, thanks for your response. My wife went through a surgery on
> Friday and is under recovery for a few days and I'm alone with the babies
> during the weekend. I'll try to find some time to create such PR tomorrow.
>
> But, before I do that, I'd like to ask: is this incompatible change really
> intentional?
>
> I mean, I can see why Raw should be the default over ERB, but shouldn't
> the resulted string be flagged as html safe by default?
>
> In other words, could you describe a real scenario where applying html
> escaping over a raw partial would make sense?
>
> I'm just curious. If you decide this change indeed worths the breakage I
> can try to submit a PR with a better warning complementing the current
> explanation.
>
> Best,
> Rodrigo.
>
>
> Em 06-05-2016 14:51, Rafael Mendonça França escreveu:
>
> That makes sense. Thank you for pointing out. Do you have a suggestion how
> to improve it? Could you open a pull request?
> On sex, 6 de mai de 2016 at 06:46 Rodrigo Rosenfeld Rosas <
> rr.ro...@gmail.com> wrote:
>
>> Here is the relevant section in the changelog, I think:
>>
>> https://github.com/rails/rails/blob/v5.0.0.beta4/actionview/CHANGELOG.md
>>
>> "Change the default template handler from ERB to Raw.
>>
>> Files without a template handler in their extension will be rendered
>> using the raw handler instead of ERB.
>>
>> Rafael Mendonça França"
>>
>> I always give it a glance to the changelogs before trying to upgrade but
>> this documented change didn't grab my attention enough to think that it
>> might impact on my application.
>>
>> There are a few performance/analytics/monitoring related scripts that
>> are loaded directly in an inline script in one of my view layouts.
>>
>> They are loaded like this:
>>
>> 

Re: [Rails-core] Significant change should be better explained in the Changelog regarding non ERB view partials

[Rafael Mendonça França]

That makes sense. Thank you for pointing out. Do you have a suggestion how
to improve it? Could you open a pull request?
On sex, 6 de mai de 2016 at 06:46 Rodrigo Rosenfeld Rosas <
rr.ro...@gmail.com> wrote:

> Here is the relevant section in the changelog, I think:
>
> https://github.com/rails/rails/blob/v5.0.0.beta4/actionview/CHANGELOG.md
>
> "Change the default template handler from ERB to Raw.
>
> Files without a template handler in their extension will be rendered
> using the raw handler instead of ERB.
>
> Rafael Mendonça França"
>
> I always give it a glance to the changelogs before trying to upgrade but
> this documented change didn't grab my attention enough to think that it
> might impact on my application.
>
> There are a few performance/analytics/monitoring related scripts that
> are loaded directly in an inline script in one of my view layouts.
>
> They are loaded like this:
>
> 

[Rails-core] [ANN] Rails 4.2.6 and 4.1.15 have been released!

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 4.2.6 and 4.1.15 have been released.

## CHANGES since 4.1.14

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.1.15/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.1.15/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v4.1.15/actionview/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.1.15/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.1.15/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.1.15/activesupport/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.1.15/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.1.14.2...v4.1.15).

## CHANGES since 4.2.5

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.2.6/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.2.6/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v4.2.6/actionview/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.2.6/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.2.6/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.2.6/activesupport/CHANGELOG.md)
* [Active Job CHANGELOG](
https://github.com/rails/rails/blob/v4.2.6/activejob/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.2.6/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.2.5.2...v4.2.6).

## SHA-1

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-1 hashes.

Here are the checksums for 4.1.15:

```
$ shasum *4.1.15.gem*
a183c8734c2f78447196a7a06c050f19bbbfe3f8  actionmailer-4.1.15.gem
18acc434397ec5a1439d89943a8611197c7b92a4  actionpack-4.1.15.gem
b40e5bf8abb6ccff18891cbf16373b3a29e13f60  actionview-4.1.15.gem
17503cf48905bf6e73439d9aa885ab2afe106e55  activemodel-4.1.15.gem
bb6b6e6a11c12a0bbd02861f7a977da00dc63830  activerecord-4.1.15.gem
4e613383b72ee1ac4085421deda1d691d1adf6d7  activesupport-4.1.15.gem
7d6cb5b79b79a6266950a2bdedacc18848ae28cd  rails-4.1.15.gem
04352395f702172a1feab498b69b77c774ac0cc9  railties-4.1.15.gem
```

Here are the checksums for 4.2.6:

```
$ shasum *4.2.6.gem*
fd754430d0bf22f72f2c5d6e312313212ebfa154  actionmailer-4.2.6.gem
ad22f1ba93836658f28a5b1890d7f34bd12d8516  actionpack-4.2.6.gem
385c05851e638be667785d2e9f125e10cf9a1226  actionview-4.2.6.gem
5431905eb16dd2d7ce3842dddc5f748f3d3da73e  activejob-4.2.6.gem
7dc2c0e48ee4124f436c1b0c963e7ca582a5a125  activemodel-4.2.6.gem
61c5eb7485cbb42f7b72e3097df159661e6ec45d  activerecord-4.2.6.gem
43538d9b6d9a40b6da44c03345841d383ea53006  activesupport-4.2.6.gem
ca802d5ecf54f085866c473d71e74c7ddf11410e  rails-4.2.6.gem
f2837b9660a9774f93c196fcf9f0e4769571a2e3  railties-4.2.6.gem
```

I'd like to thank you all, every contributor who helped with this release.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] [ANN] Rails 4.2.6.rc1 and 4.1.15.rc1 have been released!

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 4.2.6.rc1 and 4.1.15.rc1 have been
released.

If no regressions are found expect the final release this Friday, on March
4, 2016.
If you find one, please open an [issue on GitHub](
https://github.com/rails/rails/issues/new)
and mention me (@rafaelfranca) on it, so that we can fix it before the
final release.

## CHANGES since 4.1.14

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.1.15.rc1/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.1.15.rc1/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v4.1.15.rc1/actionview/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.1.15.rc1/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.1.15.rc1/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.1.15.rc1/activesupport/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.1.15.rc1/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.1.14.2...v4.1.15.rc1).

## CHANGES since 4.2.5

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.2.6.rc1/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.2.6.rc1/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v4.2.6.rc1/actionview/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.2.6.rc1/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.2.6.rc1/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.2.6.rc1/activesupport/CHANGELOG.md)
* [Active Job CHANGELOG](
https://github.com/rails/rails/blob/v4.2.6.rc1/activejob/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.2.6.rc1/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.2.5.2...v4.2.6.rc1).

## SHA-1

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-1 hashes.

Here are the checksums for 4.1.15.rc1:

```
$ shasum *4.1.15.rc1.gem*
844351646e7ef5c93b3d21eb14a3d4da0c4bd92d  actionmailer-4.1.15.rc1.gem
1ed87a6847f2f4935f0a16ffa760716f0dc3f2d2  actionpack-4.1.15.rc1.gem
343b96bfe70ebde865fc4c809978cb060a0738c4  actionview-4.1.15.rc1.gem
cc913686a9f8462015d82ea827ddc60431af0db8  activemodel-4.1.15.rc1.gem
f1ff76eb16ba627b7202b2fecaa4219228d14034  activerecord-4.1.15.rc1.gem
2e00ba29b066afe23c152c96becef01fcee3cb10  activesupport-4.1.15.rc1.gem
67a534317cb8446525b644a7abf22bd09273264a  rails-4.1.15.rc1.gem
91b4ec78e9cfcee55e8d92760b6a628ccd20a2d4  railties-4.1.15.rc1.gem
```

Here are the checksums for 4.2.6.rc1:

```
$ shasum *4.2.6.rc1.gem*
09ef4800e26fd97d3cc64d1c53ae72bc16e79fd2  actionmailer-4.2.6.rc1.gem
1f41705eec68218ea291d7cdfa233c50c1172524  actionpack-4.2.6.rc1.gem
3cbf38b5021dbb9e587e003ad1782084e323ec35  actionview-4.2.6.rc1.gem
fea55eddff554d1995868b9891e111b683bbf70c  activejob-4.2.6.rc1.gem
46d87e81f73410631554d34e0548347955a6ced4  activemodel-4.2.6.rc1.gem
9496ed951ff242d9ac0a68643877b3b213d1147a  activerecord-4.2.6.rc1.gem
07ea5df02904eed063dd5093b5a7c6f39b3e70ae  activesupport-4.2.6.rc1.gem
3c3194bc02f22e7eac12d982208418d88c0d7a70  rails-4.2.6.rc1.gem
fc855160f5d04e3997d5a09a24027d9e330959b6  railties-4.2.6.rc1.gem
```

I'd like to thank you all, every contributor who helped with this release.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] Enhancement: improved ActiveModal::Errors enumeration

[Rafael Mendonça França]

I'm positive for this enhancement. The type information is already retained
in Rails 5 but having real object could be real handy.

On Mon, Feb 29, 2016 at 12:47 PM Evan Prothro 
wrote:

> I love the concept and usability of an ActiveModel::Errors paradigm.
> However, I and others often find it frustrating to work with the
> implementation.
>
>
> I'd love to see a proper ActiveModel::Error object, where the errors
> attribute of a model including ActiveModel::Errors was an Enumerator of
> these objects.
>
>
> There are various implied benefits and added flexibility that could be
> introduced in a backwards compatible way later, and immedate benefits.
> Would love to know what y'all think about this. Happy to implement if
> desired.
>
>
> Immediate
> Benefits
>
>
> The
> error type could be retained
>
> APIs we build prefer to return Error objects to clients with the
> following schema:
>
> {
>   attribute:  "The model attribute to which the error applies. If blank, the 
> error applies generically to the base model.",
>   type:   "The type of error encountered with the model attribute or 
> model."
>   messsage:   "An internationalized message that can be displayed to a user.",
> }
>
> In particular, the type attribute allows clients to couple any logic they
> need on the error attribute and type, not themessage, which should be
> able to change with business/product needs.
>
> With a proper ActiveModel::Error object, this is easily done. With the
> current enumerable design, this is not a clean extension to make
> .
>
>
> The
> error message can be lazily looked up
>
> Currently, the message interpolation is looked up when the error is added
> to the model. This isn't necessarry, and is easily lazily evaluated when a
> derived attribute on an Error object.
>
>
>
> Other
> Enhancements easily enabled
>
>
> Accessing
> the attribute value more cleanly
>
> error = model.errors.first
> error.attribute
> => :username
> error.attribute_value
> => 'eprothro'
>
>
>
> Easier
> custom interpolation parameters
>
> # en.yml
> errors:
>   models:
> user:
>   attributes:
> username:
>   taken: "%{value} has already been taken."
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] ActiveRecord::Result#to_hash doesn't return a hash

[Rafael Mendonça França]

That method seems to be private API of Rails (at least it should be) so go
ahead to remove/deprecate it.

On Fri, Jan 22, 2016 at 1:10 PM Kache  wrote:

> Was about to open GitHub issue, but found this mailing list.
>
> [ActiveRecord::Result#to_hash](
> https://github.com/rails/rails/commit/59f7780a3454a14054d1d33d9b6e31192ab2e58b#diff-56dacac8e4a23c4e1d4f63562fa5d6d1R23
> )
>
> It's unexpected for `#to_hash` to _not_ return a hash, e.g. [AwesomePrint](
> https://github.com/michaeldv/awesome_print) checks and uses `#to_hash` to
> inspect hash-convertible objects, as noted in [an AwesomePrint issue](
> https://github.com/michaeldv/awesome_print/issues/215).
>
> Ruby core even expects `Hash` from `#to_hash`:
>
> > Hash.try_convert(ActiveRecord::Base.connection.select_all("select *
> from users limit 1;"))
> TypeError: can't convert ActiveRecord::Result to Hash
> (ActiveRecord::Result#to_hash gives Array)
>
> `#to_ary` already exists with the same implementation, meaning that users
> of `ActiveRecord::Result#to_hash` should really be using
> `ActiveRecord::Result#to_a`
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] Bump Mail dependency to pick up downstream memory improvements

[Rafael Mendonça França]

It is already allowed to use mail 2.6 with rails, so why should we disallow
to use mail < 2.6?

On Sat, Jan 23, 2016, 21:19 Karl Freeman  wrote:

> Hey all,
>
> Without wanting to claim the hard work of others!! I would love to create
> an issue that tracks bumping Mail to ~> 2.6 for Rails 5 (e.g re-create a PR
> like this one ). Here's why:
>
> Jeremyevan's PR to use a text-based columnar storage
>  in the Mime-types
> gem has been shown to significantly decrease memory when a user opts in
> to it  (I've seen
> 20mb decrease personally). This memory saving behavior is a default in
> the 3.0 release of Mime-types
> 
>  (as well as a raft of other, really lovely changes
> ).
> Given that Mail works with Mime-types 3.0
> 
>  and
> when Mail 2.6.4 has finished brewing
>  it'll
> allow Mime-types 3.0
> 
>  It
> would be great for Rails to nudge users to pick up this behavior too.
>
> What are people's views on this? It feels a little audacious of me to
> modify one line of ActionMailer's gemspec but I'm really keen to see this
> change happen.
>
> Thanks!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] Backport of keyword parameters for controller tests for Rails 4?

[Rafael Mendonça França]

I don't think it is necessary. You can still use the same syntax with Rails
4 and Rails 5, you will only see deprecations warnings, and I believe it is
acceptable in this case.

On Thu, Jan 7, 2016 at 4:33 PM Prem Sichanugrist 
wrote:

> I think that might be a good idea.
>
> Do you mind creating an issue and ping @sikachu on it? Or, do you want to
> take a crack at it? I might be able to look at this tomorrow.
>
> -Prem
>
> On Jan 7, 2016, at 11:23 AM, Markus D.  wrote:
>
> +1 Would really ease transition to Rails 5 if I could write my tests the
> new way already in Rails 4.
>
> Am Freitag, 12. Juni 2015 04:10:33 UTC+2 schrieb Victor Costan:
>>
>> I'm trying to add Rails 5 support to an engine which (among other things)
>> has a generator for controller tests.
>>
>> I've ran into the keyword arguments deprecation warning at the bottom of
>> this e-mail, and I'm in a bind now. If I use keyword arguments to get rid
>> of the warnings, I lose Rails 4 compatibility.
>>
>> So far, I've managed to write tests that work in current Rails and
>> previous Rails, and I hope I'll be able to do that in the future. Is there
>> any chance that the keyword arguments will be backported to Rails 4 via a
>> gem, like strong_parameters were backported to Rails 3?
>>
>> Thank you,
>> Victor
>>
>>
>>
>> DEPRECATION WARNING: ActionController::TestCase HTTP request methods will
>> accept only
>> keyword arguments in future Rails versions.
>>
>> Examples:
>>
>> get :show, params: { id: 1 }, session: { user_id: 1 }
>> process :update, method: :post, params: { id: 1 }
>>
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] Reducing ActionCable dependencies?

[Rafael Mendonça França]

Mike,

the Rails core already agreed that this would be the best direction but
nobody yet had time to work on this.

If you want to work on this it would be awesome.

Let us know if you need something from our side. If you want to discuss I
can invite you to our private Basecamp project.



On Tue, Jan 5, 2016 at 9:55 PM Mike Perham  wrote:

> I've noticed that Rails's gem dependency count has gone from 34 in 4.2.4
> to 55 in 5.0.beta1.  I think much of this is due to pulling in all of
> Celluloid and EventMachine via ActionCable.  I'd be interesting in working
> to minimize this footprint, perhaps by using concurrent-ruby's thread pools
> rather than celluloid actors.
>
> Is there any interest in me pursuing this work?  Has anyone else
> investigated in this direction?
>
> Mike
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] Any reason #in_batches is not backported to Rails 4.x?

[Rafael Mendonça França]

New features are not backported to stable branches. See our maintenance
policy http://guides.rubyonrails.org/maintenance_policy.html#new-features

On Wed, Dec 23, 2015 at 3:32 PM Kashyap Kondamudi 
wrote:

> Hello
>
> The `ActiveRecord::Relation#in_batches`, similar to
> `ActiveRecord::Relation#find_in_batches`, but which yields a collection
> ofActiveRecord::Relation objects has been merged into master via
> https://github.com/rails/rails/pull/20933. If I'm not mistaken, this is
> not backported to older Rails versions—I've checked out the v4.2.5.rc2
> tag, but couldn't find the method.
>
> Is there a reason why this is not backported to older Rails versions?
>
>
> --
> Kashyap Kondamudi
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] Deprecation warnings after changing to Rails 5/beta1

[Rafael Mendonça França]

Hi Al, this is a now issue. The turbolinks release that will be included in
rails 5 is still in work in progress. These warnings will go when
turbolinks 5 is released

On Sat, Dec 19, 2015, 06:56 Al  wrote:

> Wanted to document this somewhere.
>
>- If you want to use Rails 5.0.0.beta1
>- and you use rails/turbolinks (current released version/2.5.3)
>- and you are getting these messages:
>
> DEPRECATION WARNING: alias_method_chain is deprecated. Please, use
> Module#prepend instead. From module, you can access the original
> method using super. (called from block in tsort_each at
> .../.rvm/rubies/ruby-2.3.0-preview2/lib/ruby/2.3.0/tsort.rb:228)
>
> DEPRECATION WARNING: before_filter is deprecated and will be removed
> in Rails 5.1. Use before_action instead. (called from 
> at .../app/controllers/application_controller.rb:1)
>
>- then if you change you Gemfile to:
>
> gem 'turbolinks', github: 'rails/turbolinks'
>
>
>- then you will get a clean "rake" run.
>
> Tell me if I need to write an issue somewhere.
>
>
> Thanks,
>
> Al
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at https://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at https://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] [ANN] Rails 4.2.5.rc2 and 4.1.14.rc2 have been released!

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 4.2.5.rc2 and 4.1.14.rc2 have been
released.

If no regressions are found expect the final release this Wednesday, on
November 11, 2015.
If you find one, please open an [issue on GitHub](
https://github.com/rails/rails/issues/new)
and mention me (@rafaelfranca) on it, so that we can fix it before the
final release.

## CHANGES since 4.1.13

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.1.14.rc2/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.1.14.rc2/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v4.1.14.rc2/actionview/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.1.14.rc2/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.1.14.rc2/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.1.14.rc2/activesupport/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.1.14.rc2/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.1.13...v4.1.14.rc2).

## CHANGES since 4.2.4

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.2.5.rc2/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.2.5.rc2/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v4.2.5.rc2/actionview/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.2.5.rc2/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.2.5.r2/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.2.5.rc2/activesupport/CHANGELOG.md)
* [Active Job CHANGELOG](
https://github.com/rails/rails/blob/v4.2.5.rc2/activejob/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.2.5.rc2/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.2.4...v4.2.5.rc2).

## SHA-1

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-1 hashes.

Here are the checksums for 4.1.14.rc2:

```
$ shasum *4.1.14.rc2*
7c546616f87939a01807a55e78ed8494acc7c2ec  actionmailer-4.1.14.rc2.gem
8f80145fa65746c8a0a5492ae6213f447bbb0aaa  actionpack-4.1.14.rc2.gem
f0186571e89372ffbea47fbc4a3b901e46b0760e  actionview-4.1.14.rc2.gem
558e4eabcd1cec6a5089348dfd5a6f949d7606cc  activemodel-4.1.14.rc2.gem
0db20360a75bfa74b6539df190af8920bd75ff2f  activerecord-4.1.14.rc2.gem
3a2608827b895234e3d3b99e95df29344e31f875  activesupport-4.1.14.rc2.gem
5a9bd84dbc15a06128fc71d197cd6ee3d783114a  rails-4.1.14.rc2.gem
742da45dc3d63b43c882d7ce1d71f682bd1149c0  railties-4.1.14.rc2.gem
```

Here are the checksums for 4.2.5.rc2:

```
$ shasum *4.2.5.rc2*
d8fa2707c7f88aaf033b6ef2f0e39b5805823a8b  actionmailer-4.2.5.rc2.gem
80e43409399bcf3377c4a1aab803c442a635cadb  actionpack-4.2.5.rc2.gem
21d4a14dfec4ccfb321d51c1a73854f7c90003e0  actionview-4.2.5.rc2.gem
c1e258c2ed4b4e91b6d2f31d1a2020179043b5ba  activejob-4.2.5.rc2.gem
72f86e0ccb22e1b0f2980b500f1d7ced4d887da1  activemodel-4.2.5.rc2.gem
dc8cbcd461f3d3b583ac18c2d3c4fc5a8857ce72  activerecord-4.2.5.rc2.gem
40b5b72140f30bc97b7dc9e30c12d86ade0692b8  activesupport-4.2.5.rc2.gem
d3b7ee2ef71d9a9a4cb0a237162a67393549eeed  rails-4.2.5.rc2.gem
5969ef6ef00239fb5d2b012eb23068f1620a2563  railties-4.2.5.rc2.gem
```

I'd like to thank you all, every contributor who helped with this release.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] link_to_if/link_to_unless inconsistencies

[Rafael Mendonça França]

If that is possible without breaking backward compatibility go ahead, but I
can't think in a way to make it backward compatible.

On Thu, Nov 5, 2015 at 2:00 PM Kevin Deisz <kevin.de...@gmail.com> wrote:

> I get that that's the way that it works, my point was that it's
> inconsistent. Right now you can't achieve the normal link_to behavior when
> the condition is met. We can preserve the behavior for the negative case
> and still get the content_tag block benefit for the positive case.
>
> On Thu, Nov 5, 2015 at 3:54 PM, Rafael Mendonça França <
> rafaelmfra...@gmail.com> wrote:
>
>> It is the way they work. See the documentation. The block is used only
>> when the condition is not met.
>>
>> On Thu, Nov 5, 2015 at 1:26 PM Kevin Deisz <kevin.de...@gmail.com> wrote:
>>
>>> Hi there,
>>>
>>> Seems like in the positive condition, link_to_if and link_to_unless are
>>> inconsistent. When I send a block to link_to (or for that matter anything
>>> else that calls content_tag) the block is used to determine the content in
>>> the case that "name" is not provided. It gets around this by shifting the
>>> args, effectively, as in (html_options, options, name = options, name,
>>> block if block_given?).
>>>
>>> However, with link_to_if/link_to_unless, when the condition is met it
>>> always uses the main content. As in:
>>>
>>> link_to_if(true, root_path) do
>>>   My Link <%= some_helper %>
>>> end
>>>
>>> looks like "/" in the UI and the block is ignored. I'd love to fix this,
>>> but want to make sure there isn't some good reason first.
>>>
>>> Thanks.
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Ruby on Rails: Core" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to rubyonrails-core+unsubscr...@googlegroups.com.
>>> To post to this group, send email to rubyonrails-core@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/rubyonrails-core.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Ruby on Rails: Core" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to rubyonrails-core+unsubscr...@googlegroups.com.
>> To post to this group, send email to rubyonrails-core@googlegroups.com.
>> Visit this group at http://groups.google.com/group/rubyonrails-core.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> *Kevin D. Deisz*
> DrugDev TrialNetworks
> Senior Software Engineer
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at http://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] link_to_if/link_to_unless inconsistencies

[Rafael Mendonça França]

It is the way they work. See the documentation. The block is used only when
the condition is not met.

On Thu, Nov 5, 2015 at 1:26 PM Kevin Deisz  wrote:

> Hi there,
>
> Seems like in the positive condition, link_to_if and link_to_unless are
> inconsistent. When I send a block to link_to (or for that matter anything
> else that calls content_tag) the block is used to determine the content in
> the case that "name" is not provided. It gets around this by shifting the
> args, effectively, as in (html_options, options, name = options, name,
> block if block_given?).
>
> However, with link_to_if/link_to_unless, when the condition is met it
> always uses the main content. As in:
>
> link_to_if(true, root_path) do
>   My Link <%= some_helper %>
> end
>
> looks like "/" in the UI and the block is ignored. I'd love to fix this,
> but want to make sure there isn't some good reason first.
>
> Thanks.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at http://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] [ANN] Rails 4.2.5.rc1 and 4.1.14.rc1 have been released!

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 4.2.5.rc1 and 4.1.14.rc1 have been
released.

If no regressions are found expect the final release this Wednesday, on
November 4, 2015.
If you find one, please open an [issue on GitHub](
https://github.com/rails/rails/issues/new)
and mention me (@rafaelfranca) on it, so that we can fix it before the
final release.

## CHANGES since 4.1.13

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.1.14.rc1/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.1.14.rc1/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v4.1.14.rc1/actionview/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.1.14.rc1/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.1.14.rc1/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.1.14.rc1/activesupport/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.1.14.rc1/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.1.13...v4.1.14.rc1).

## CHANGES since 4.2.4

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.2.5.rc1/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.2.5.rc1/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v4.2.5.rc1/actionview/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.2.5.rc1/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.2.5.rc1/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.2.5.rc1/activesupport/CHANGELOG.md)
* [Active Job CHANGELOG](
https://github.com/rails/rails/blob/v4.2.5.rc1/activejob/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.2.5.rc1/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.2.4...v4.2.5.rc1).

## SHA-1

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-1 hashes.

Here are the checksums for 4.1.14.rc1:

```
$ shasum *4.1.14.rc1*
6c4513c4f2a57d11fe8e9abafacde175a284a0fc  actionmailer-4.1.14.rc1.gem
27eeb9c788be0323eb459edda2b4d09418f37c40  actionpack-4.1.14.rc1.gem
2f70d52109b8be2c2dfbc57992fb1070a3a49fc5  actionview-4.1.14.rc1.gem
d3aafc6b61999fa0c9a363dfc626c93df9e460a2  activemodel-4.1.14.rc1.gem
55ea63bcca5925652956d194e8dbf4aca1780888  activerecord-4.1.14.rc1.gem
f771aa7d47c8a390449f577024d9335f7487294e  activesupport-4.1.14.rc1.gem
b3a16b8372ec44927196d38a12cc72fc97ad54c8  rails-4.1.14.rc1.gem
f1be582957f2494e13462f464e28afbaf938d233  railties-4.1.14.rc1.gem
```

Here are the checksums for 4.2.5.rc1:

```
$ shasum *4.2.5.rc1*
95125668842661dda2db412a45226f9b1219b522  actionmailer-4.2.5.rc1.gem
d9c6b7e38f9eab5975ca2549cb88b6700a0acdfd  actionpack-4.2.5.rc1.gem
f40ad9c7a5cd2c4b14f96615fdf5627d4fcaa9f3  actionview-4.2.5.rc1.gem
edcc197c162d64d663cf1049851105777c9a41ff  activejob-4.2.5.rc1.gem
eff7203c26da06c76a667428c70dc8741afac67e  activemodel-4.2.5.rc1.gem
c719ffeaffbd0f3bc1e23ed1db32df84662c0460  activerecord-4.2.5.rc1.gem
311d02a075d1669eba52b026ac60b834e02e96c6  activesupport-4.2.5.rc1.gem
810f02ff2930062f269340bc7df4e4e213a168a3  rails-4.2.5.rc1.gem
e7f842b19b4e3f67625d3df3127ed99392f19bed  railties-4.2.5.rc1.gem
```

I'd like to thank you all, every contributor who helped with this release.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] Suggesting an alternative to raising a file missing exception in `config_for`

[Rafael Mendonça França]

I see the file not being there an exceptional case. Making config_for not
raise if the file doesn't exists can lead to more problems like not reading
the config file because of a typo in the file name.

```
if config_for(:rdis)
  # configure the thing
else
  # don't configure the thing
end
```

The block version would be weird too:

```
redis_config = config_for(:redis) do
  # don't configure the thing
end

Redis.config = redis_config
```

The only solution that would work is the helper to check the file existence.


On Wed, Oct 28, 2015 at 5:38 PM Chris Nicola  wrote:

> Currently `Application#config_for` raises an exception whenever a config
> file isn't found. However, this doesn't really seem very exceptional to me
> and there are going to be a lot of times where I want to configure an
> application module only if the configuration is available and something
> else if it isn't.
>
> I could of course check if the file exists on my own, but then that almost
> entirely defeats the convenience of this convenience function.
>
> A few possible solutions:
>
>  Offer an easy way to check if the file exists like `config_exists?`
>
> I don't like this because it feels too much like a nil checking pattern.
>
>  Allow config_for to accept a block or argument
>
> This is similar to the `Hash#fetch` pattern, and the value of the block
> can be returned to the caller. The default exception behavior can remain if
> no value or block is provided. This would also allow for a few patterns.
>
> 1. Provide alternative configuration logic when the file isn't found
> 2. Don't configure the component when the file isn't found and log a
> warning
>
> For example:
>
> ```
> if config_for(:the_thing, false)
>   # configure the thing
> else
>   # don't configure the thing
>   logger.warn "The thing is not configured, no configuration file is found
> end
> ```
>
> I'm definitely open to other suggestions, but the way `config_for` works
> right now I'm very hesitant to use it.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at http://groups.google.com/group/rubyonrails-core.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] [ANN] Rails 4.2.4 and 4.1.13 have been released!

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 4.2.4 and 4.1.13 have been released.

No regressions were found so these releases include the same changes that
the release candidates.

## CHANGES since 4.1.12

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.1.13/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.1.13/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v4.1.13/actionview/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.1.13/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.1.13/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.1.13/activesupport/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.1.13/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.1.12...v4.1.13).

## CHANGES since 4.2.3

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.2.4/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.2.4/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v4.2.4/actionview/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.2.4/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.2.4/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.2.4/activesupport/CHANGELOG.md)
* [Active Job CHANGELOG](
https://github.com/rails/rails/blob/v4.2.4/activejob/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.2.4/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.2.3...v4.2.4).

## SHA-1

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-1 hashes.

Here are the checksums for 4.1.13:

```
$ shasum *4.1.13*
7c637fed154a152451adb8ef1ebae136e0502ebd  actionmailer-4.1.13.gem
61303b7ee877aa06f16ce0ba6a7cce21ca031f42  actionpack-4.1.13.gem
39c5a4a290a5969402bf5c4ac61b99e5dcb40c3c  actionview-4.1.13.gem
6d88159aa15ea48f9118ece97ec549807a504f55  activemodel-4.1.13.gem
1107470b19cc0d6608d431678c78d3871c8df229  activerecord-4.1.13.gem
f79bdfa0105c1a833069d989291ec9d23bc84d92  activesupport-4.1.13.gem
6391b4a323e0b30118ffdbad6bb5f68459920d7b  rails-4.1.13.gem
fc64a4f89a3fa8f9ab2a9edd37d7338a79cb9859  railties-4.1.13.gem
```

Here are the checksums for 4.2.4:

```
$ shasum *4.2.4*
a866394bb4682afaa6d54458b1f3be0dca5e862e  actionmailer-4.2.4.gem
b625e58fb8fa11185ff81630f3bef5c517e294e4  actionpack-4.2.4.gem
334ddc60724e4e1ff99e2170d2e435805d0ade0b  actionview-4.2.4.gem
7bd46253f17bcff5c8ae3ba0f0938c38b0ca1e2f  activejob-4.2.4.gem
d361d1e0eac7851103ac2de4c9359a556c724ab9  activemodel-4.2.4.gem
d9faecb759827fc7944558463388efbbd9f20005  activerecord-4.2.4.gem
ab4283126725e3aa9c248e2e2119548ad205732d  activesupport-4.2.4.gem
67d7a12105f5389dd7b511eff5f56c6c048175d8  rails-4.2.4.gem
8e9eab180dbd97eaf7626601c55e61ea1ae68284  railties-4.2.4.gem
```

I'd like to thank you all, every contributor who helped with this release.

-- 
You received this message because you are subscribed to the Google Groups Ruby 
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] [ANN] Rails 4.2.4.rc1 and 4.1.13.rc1 have been released!

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 4.2.4.rc1 and 4.1.13.rc1 have been
released.

If no regressions are found expect the final release this Wednesday, on
August 19, 2015.
If you find one, please open an [issue on GitHub](
https://github.com/rails/rails/issues/new)
and mention me (@rafaelfranca) on it, so that we can fix it before the
final release.

## CHANGES since 4.1.12

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.1.13.rc1/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.1.13.rc1/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v4.1.13.rc1/actionview/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.1.13.rc1/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.1.13.rc1/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.1.13.rc1/activesupport/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.1.13.rc1/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.1.12...v4.1.13.rc1).

## CHANGES since 4.2.3

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.2.4.rc1/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.2.4.rc1/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v4.2.4.rc1/actionview/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.2.4.rc1/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.2.4.rc1/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.2.4.rc1/activesupport/CHANGELOG.md)
* [Active Job CHANGELOG](
https://github.com/rails/rails/blob/v4.2.4.rc1/activejob/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.2.4.rc1/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.2.3...v4.2.4.rc1).

## SHA-1

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-1 hashes.

Here are the checksums for 4.1.13.rc1:

```
$ shasum *4.1.13.rc1*
284f1eb3a000d54f07435e0b19e88f1ba80f738b  actionmailer-4.1.13.rc1.gem
352ad673a18efe226ed3e1b1eb7e61818ccae1a2  actionpack-4.1.13.rc1.gem
f7e147aa4377149a7516bf23fa5892979a7ff77f  actionview-4.1.13.rc1.gem
70da96abb737ef31eba8e1b57fa2cb122110bb59  activemodel-4.1.13.rc1.gem
c571e1092a3982517d353ff85fab2c5e9b3c28cc  activerecord-4.1.13.rc1.gem
19e9f8f248261d6b605c62eca071e29e9c7e5a90  activesupport-4.1.13.rc1.gem
7c418986f10ff82fbb1be1b3a6c9defb80aac5eb  rails-4.1.13.rc1.gem
e5ca51e2cb32fa57bd7ba18f8fe52cd3c0e2bbb9  railties-4.1.13.rc1.gem
```

Here are the checksums for 4.2.4.rc1:

```
$ shasum *4.2.4.rc1*
7f343fd97d1e41920feac65020fa487c4d0be67e  actionmailer-4.2.4.rc1.gem
f815f40569f0e6b93f10c61d696d9ab06aba6531  actionpack-4.2.4.rc1.gem
bca83efa6384b88b5429f1dad1dd1a05e7c8e491  actionview-4.2.4.rc1.gem
7d8694143e23712da67606ea78919ed71605dd19  activejob-4.2.4.rc1.gem
674d0fd053f8365a1be9fe787f6fe10c5b9b3993  activemodel-4.2.4.rc1.gem
ec34623a19a136dcb62308ad3dfeba3209a5beac  activerecord-4.2.4.rc1.gem
8673028f02630357ea1f086323468b4a733b00aa  activesupport-4.2.4.rc1.gem
970ee741e3e2ffcaae6cbb33895ee2dc407bb5a3  rails-4.2.4.rc1.gem
69f16c95fac8739bc62e5f2cbe352bfa05746223  railties-4.2.4.rc1.gem
```

I'd like to thank you all, every contributor who helped with this release.

-- 
You received this message because you are subscribed to the Google Groups Ruby 
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] Re: Nokogiri adds a lot of weight to ActionView

[Rafael Mendonça França]

I think it is worth to experiment yes, I don't want to decline anything
without seeing the code and how it would feel. I can see advantages of
doing that.

On Mon, Aug 10, 2015 at 2:11 PM iybet...@gmail.com wrote:

 Rafael,

 I made 3 strong arguments in response to your point about capybara.  I
 would have appreciated a response explaining if any of my reasoning is
 wrong here.

 This is not a difficult PR and I still feel the case for it is strong but
 I don't want to start working on it while I'm waiting to hear from you.


 On Monday, July 13, 2015 at 6:37:28 PM UTC-4, iybe...@gmail.com wrote:

 Rails goes out of its way to avoid forcing an installation of bcrypt
 because it is a binary library.  See
 https://github.com/rails/rails/blob/v4.2.3/Gemfile#L21

 Nokogiri forces installation of 2 binary libraries (libxml2 and libxslt),
 so one would expect it not to be a dependency of any of the core components
 of Rails.

 However, starting with actionview 4.2.0, nokogiri is now a dependency.

 That means every time actionview appears in a Gemfile.lock, so does
 nokogiri.  I would often include ActionView 4.1 in non-Rails projects just
 to use number_to_currency, but now with the nokogiri dependency, the
 overhead is hardly worth it.

 Consider the fact that I'm deploying about 5 such projects to the same
 server, all using separate BUNDLE_PATH's.  That means 5 installations of
 nokogiri, none of which are being used.  This adds time to every
 `capistrano bundler:install` and a significant amount of disk space is
 wasted on this.  For any other gem, this wouldn't make much of a
 difference, but nokogiri is really big and takes a long time to install,
 and Rails has already set a precedent by not including the (much lighter)
 bcrypt.

 Is the rails-core team open to the following solutions:
 ---

 1) Separate the parts of actionview that depend on rails-dom-testing into
 a separate gem

 Create an actionview-testing gem, which would only be necessary in the
 Gemfile's test group, thus saving even more overhead in production.  This
 would depend on action-view and rails-dom-testing, but actionview would not
 depend on rail-dom-testing.

 (The same approach that I suggest below for rails-html-sanitizer might
 work for rails-dom-testing too, but it may add more complexity that carving
 a separate gem--there are multiple code paths that can lead you to
 rails-dom-testing methods, whereas there's a single method that's a
 bottleneck for all entries to rails-html-sanitizer.)
 ---

 2) In ActionView::Helpers::SanitizeHelper, move `require
 rails-html-sanitizer` into the  #sanitizer_vendor method.

 If a LoadError is raised, handle it just as we do for bcrypt:
 https://github.com/rails/rails/blob/v4.2.3/activemodel/lib/active_model/secure_password.rb#L60

 Add rails-html-sanitizer to the Gemfile template so that it's
 automatically in new Rails projects.  Only upgrades and would need to
 manually add this to the Gemfile, so we would have to add it to the upgrade
 guide.  Standalone actionview projects would also need to add it to their
 Gemfile, but *rafaelfranca https://github.com/rafaelfranca* has
 assured me that non-Rails projects should never be using
 rails-html-sanitizer anyway:
 https://github.com/rails/rails-html-sanitizer/issues/25#issuecomment-60833972
 .
 ---

 I would love to get started on a PR.  I just need to know if it will be
 considered.





 --
 You received this message because you are subscribed to the Google Groups
 Ruby on Rails: Core group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to rubyonrails-core+unsubscr...@googlegroups.com.
 To post to this group, send email to rubyonrails-core@googlegroups.com.
 Visit this group at http://groups.google.com/group/rubyonrails-core.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups Ruby 
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] Feature proposal: Silently skip add with before_add association callback using false

[Rafael Mendonça França]

Thank you for the suggestion.

All callbacks now are only skipped if an exception is raised and we are
removing the special meaning of false, so I think this behavior correct.

On Tue, Aug 4, 2015 at 4:48 PM Bruno Macabeus bruno.macab...@gmail.com
wrote:

 As stated in the documentation
 http://guides.rubyonrails.org/association_basics.html#association-callbacks:
 *If a before_add callback throws an exception, the object does not get
 added to the collection*

 This way to prevent that save is very ugly.
 It would be better to keep the standard of the other callback (like
 before_create): if it returns false, not saved.
 Others users would also like it that way
 http://stackoverflow.com/questions/7273792/silently-skip-add-with-before-add-association-callback-instead-of-raising-an-exc
 .

 --
 You received this message because you are subscribed to the Google Groups
 Ruby on Rails: Core group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to rubyonrails-core+unsubscr...@googlegroups.com.
 To post to this group, send email to rubyonrails-core@googlegroups.com.
 Visit this group at http://groups.google.com/group/rubyonrails-core.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups Ruby 
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] TimeHelpers and DateTime

[Rafael Mendonça França]

It does now at master branch.

On Wed, Jul 22, 2015 at 9:05 PM Tyler Margison kolor...@gmail.com wrote:

 I haven't been able to find anything about this by searching, on Google or
 GitHub, but you cannot use TimeHelpers and DateTime together. Is there a
 reason the travel_to function doesn't stub DateTime.now or is this just
 an oversight?

 --
 You received this message because you are subscribed to the Google Groups
 Ruby on Rails: Core group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to rubyonrails-core+unsubscr...@googlegroups.com.
 To post to this group, send email to rubyonrails-core@googlegroups.com.
 Visit this group at http://groups.google.com/group/rubyonrails-core.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups Ruby 
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] Re: Nokogiri adds a lot of weight to ActionView

[Rafael Mendonça França]

Nokogiri is needed for tests and I don't think tests are often used, at
least they should. I still don't see any reason for doing this even more
because almost all Rails applications use capybara and nokogiri is also a
capybara dependency.

On Tue, Jul 14, 2015 at 10:47 AM iybet...@gmail.com wrote:

 Thank you for the feedback.  Thank you especially to Carlos for pointing
 out that I could just include ActiveSupport without ActionView.

 I could have left out the personal anecdote--Ryan makes a good point that
 the real issue is that nokogiri should not be a dependency when it is
 needed by only a small subset of functionality, that often is not used at
 all.

 So, rails-core team, are you guys on board?

 --
 You received this message because you are subscribed to the Google Groups
 Ruby on Rails: Core group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to rubyonrails-core+unsubscr...@googlegroups.com.
 To post to this group, send email to rubyonrails-core@googlegroups.com.
 Visit this group at http://groups.google.com/group/rubyonrails-core.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups Ruby 
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] Optional locale argument for pluralize helper

[Rafael Mendonça França]

:shipit:

On Tue, Jul 7, 2015 at 1:45 PM Stefan Daschek ste...@daschek.net wrote:

  Since Rails 4 it’ possible to use locale-specific pluralization rules by
 doing something like Produkt.pluralize(:de).

 Is there any reason why ActionView::Helpers::TextHelper#pluralize doesn’t
 accept an (optional) locale argument, too?

 Sample usage (in a view or helper):
 pluralize(Product.count, Produkt, locale: :de)

 As far as I can see, adding an optional keyword argument to
 https://github.com/rails/rails/blob/master/actionview/lib/action_view/helpers/text_helper.rb#L220
 shouldn’t be a problem regarding backwards compatibility.

 Should I prepare a pull request?

 Thanks,
 Stefan
 ​

 --
 You received this message because you are subscribed to the Google Groups
 Ruby on Rails: Core group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to rubyonrails-core+unsubscr...@googlegroups.com.
 To post to this group, send email to rubyonrails-core@googlegroups.com.
 Visit this group at http://groups.google.com/group/rubyonrails-core.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups Ruby 
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] [ANN] Rails 4.2.3 and 4.1.12 have been released!

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 4.2.3 and 4.1.12 have been released.

No regressions were found so these releases include the same changes that
the release candidates.

## CHANGES since 4.1.11

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.1.12/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.1.12/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v4.1.12/actionview/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.1.12/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.1.12/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.1.12/activesupport/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.1.12/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.1.11...v4.1.12).

## CHANGES since 4.2.2

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.2.3/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.2.3/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v4.2.3/actionview/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.2.3/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.2.3/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.2.3/activesupport/CHANGELOG.md)
* [Active Job CHANGELOG](
https://github.com/rails/rails/blob/v4.2.3/activejob/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.2.3/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.2.2...v4.2.3).

## SHA-1

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-1 hashes.

Here are the checksums for 4.1.12:

```
$ shasum *4.1.12*
c4f8aebcd59011e47d373a99413dad210e3d4bbd  actionmailer-4.1.12.gem
ce8868972769ad56b93b7b98585d64804d6d8174  actionpack-4.1.12.gem
2d6e6c6212bff10993394c63b56ce434342c9a47  actionview-4.1.12.gem
9a462b3ad2cfaf5f7914869efd5e8c62e54064b0  activemodel-4.1.12.gem
c0d65ed4f79115f7a9901d60201e720a7f556335  activerecord-4.1.12.gem
97fd3230896d900923dc650e788ccaaf3b06d692  activesupport-4.1.12.gem
9f6db196328b302c4c3a7ff3a1c7cd1a191221cc  rails-4.1.12.gem
8c7c04045df2eebc69e54c8426def69eca0f8bf6  railties-4.1.12.gem
```

Here are the checksums for 4.2.3:

```
$ shasum *4.2.3*
f02da8c3896d4c8cd208b7c555c2c2235e44ce0e  actionmailer-4.2.3.gem
d824941013ba3616aa643d4c5016d00bf2dc028f  actionpack-4.2.3.gem
53982ad7579069c2a5de4939bb8c689550bdd2ab  actionview-4.2.3.gem
280e774caf7335aba1b50441b4890803d18a666c  activejob-4.2.3.gem
0d2160b37223703d167cfd5a8cb358029ccbacd9  activemodel-4.2.3.gem
8799d638cc5cdbd59296392f0f1014a051378517  activerecord-4.2.3.gem
1dc5e9cba144dc9794bc4ebed19a8528b7287a76  activesupport-4.2.3.gem
0ef8f13382996c3480d09900e34988aae85f0886  rails-4.2.3.gem
0fa6b51c3e9f70f0ce9fb1d1977169537d19ae86  railties-4.2.3.gem
```

I'd like to thank you all, every contributor who helped with this release.

-- 
You received this message because you are subscribed to the Google Groups Ruby 
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] Re: RFC: Rails-API: Proposed better interface for registering serializers with the controller

[Rafael Mendonça França]

Go for it, this will improve the way different serializers hook inside
Rails so I don't see any reason to not do so.

On Wed, Jun 24, 2015 at 1:07 PM Benjamin Fleischer bfleisc...@gmail.com
wrote:

 I'm a little bummed no one responded to this.  Here's some new info:
 ActiveModelSerializers already mixes in `get_serializer` to controllers.
 https://github.com/rails-api/active_model_serializers/blob/f67fd976ecbe41305c484e4689003758e8631998/lib/action_controller/serialization.rb#L21-L30

 In AMS PR #954
 https://github.com/rails-api/active_model_serializers/pull/954 I've moved
 the serialization logic there from _render_with_renderer_json
 https://github.com/rails-api/active_model_serializers/blob/728b939521321f0bbe6680d4d070a4b63a1ca404/lib/action_controller/serialization.rb#L22-L49


 - def get_serializer(resource)- @_serializer ||= @_serializer_opts.delete(
 :serializer)- @_serializer ||= ActiveModel::Serializer
 .serializer_for(resource)-- if @_serializer_opts.key?(:each_serializer)-
 @_serializer_opts[:serializer] = @_serializer_opts.delete(:each_serializer
 )+ def get_serializer(resource, options = {})+ serializable_resource =
 ActiveModel::Serializer::build(resource, options) do |builder|+ if
 builder.serializer?+ builder.serialization_scope ||= serialization_scope+
 builder.serialization_scope_name = _serialization_scope+ builder.adapter+
 else+ resource+ end end-- @_serializer end
  [:_render_option_json, :_render_with_renderer_json].each do |
 renderer_method| define_method renderer_method do |resource, options|-
 @_adapter_opts, @_serializer_opts =- options.partition { |k, _|
 ADAPTER_OPTION_KEYS.include? k }.map { |h| Hash[h] }-- if use_adapter? 
 (serializer = get_serializer(resource))-- @_serializer_opts[:scope] ||=
 serialization_scope- @_serializer_opts[:scope_name] = _serialization_scope
 -- # omg hax- object = serializer.new(resource, @_serializer_opts)-
 adapter = ActiveModel::Serializer::Adapter.create(object, @_adapter_opts)-
 super(adapter, options)


-- 
You received this message because you are subscribed to the Google Groups Ruby 
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] [ANN] Rails 4.2.3.rc1 and 4.1.12.rc1 have been released!

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 4.2.3.rc1 and 4.1.12.rc1 have been
released.

If no regressions are found expect the final release this Thursday, on June
25, 2015.
If you find one, please open an [issue on GitHub](
https://github.com/rails/rails/issues/new)
and mention me (@rafaelfranca) on it, so that we can fix it before the
final release.

## CHANGES since 4.1.11

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.1.12.rc1/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.1.12.rc1/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v4.1.12.rc1/actionview/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.1.12.rc1/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.1.12.rc1/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.1.12.rc1/activesupport/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.1.12.rc1/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.1.11...v4.1.12.rc1).

## CHANGES since 4.2.2

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.2.3.rc1/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.2.3.rc1/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v4.2.3.rc1/actionview/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.2.3.rc1/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.2.3.rc1/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.2.3.rc1/activesupport/CHANGELOG.md)
* [Active Job CHANGELOG](
https://github.com/rails/rails/blob/v4.2.3.rc1/activejob/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.2.3.rc1/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.2.2...v4.2.3.rc1).

## SHA-1

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-1 hashes.

Here are the checksums for 4.1.12.rc1:

```
$ shasum *4.1.12.rc1*
5309022944d12fcf015f8993db2c69f66d0fa9c4  actionmailer-4.1.12.rc1.gem
7e66207c9bd27bd07966a93e4a14abbf792920d7  actionpack-4.1.12.rc1.gem
17a9c55edf3988a28af2017f901bcbcc7257c99a  actionview-4.1.12.rc1.gem
78a04199bb509617d672e62076a704849b90650d  activemodel-4.1.12.rc1.gem
b7ffcf6ac2c9929d18e406dfb9fd6b9858d3d893  activerecord-4.1.12.rc1.gem
c8bbbc325547bd3707b445e79c95406e057037c2  activesupport-4.1.12.rc1.gem
a3307e12472796620e1e7b3b71ce1e0c6a112854  rails-4.1.12.rc1.gem
dfd11e7529f6b21049644c16b62e53d898ce4013  railties-4.1.12.rc1.gem
```

Here are the checksums for 4.2.3.rc1:

```
$ shasum *4.2.3.rc1*
3af2c0a834e8f6c26656720419bedc2935df4424  actionmailer-4.2.3.rc1.gem
bdf102b742a963d3b1697e4e876900c1644fe502  actionpack-4.2.3.rc1.gem
94020ee0a2372d601de8c2e62a672ea35d1548cd  actionview-4.2.3.rc1.gem
f9429285835d11a9de31f51349d35f75bf242a02  activejob-4.2.3.rc1.gem
92cedde54d1c3951ed431825b36e6868b5c79142  activemodel-4.2.3.rc1.gem
9cafdd1bd85ca8a61c73f2cb31973cc4074c252f  activerecord-4.2.3.rc1.gem
8c2740af13ff4e664edef95f49a1e7536168e8fa  activesupport-4.2.3.rc1.gem
a1eeaaa8e7bb3a2f9ee29bf5525eaea54313a4a6  rails-4.2.3.rc1.gem
8aa764a9befa9ecad476bb7d07403da4ceea67a6  railties-4.2.3.rc1.gem
```

I'd like to thank you all, every contributor who helped with this release.

-- 
You received this message because you are subscribed to the Google Groups Ruby 
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] proposal: deprecate save() in favor of save!()

[Rafael Mendonça França]

I think the documentation is very clear about this:

Saves the model.
If the model is new a record gets created in the database, otherwise
the existing record gets updated.
By default, save always run validations. If any of them fail the
action is cancelled and save returns false.

If it is not we should fix the documentation but for me it is not a good
idea to rename save to try_save. The Rails conventions for bang methods are
clear.
​


On Mon, Jun 22, 2015 at 11:24 AM pseidemann p...@zattoo.com wrote:

 hello,

 currently in rails you have two methods to save a record: `save` and
 `save!`.
 I think `save` is often used wrong because the return value is not always
 checked.
 even the documentation is not very clear about the subtle different about
 the two methods. for `save` the first sentence is:
  Saves the model.

 it's not clearly mentioned there that it will _not_ save the model at all
 when validation fails. so developers will introduce bugs when not always
 checking for the return value e.g. in delayed job methods or in rake tasks
 (or maybe even in controllers).

 my proposal would be to deprecate the usage of `save` and introduce a new
 method called `try_save` which has the same implementation as the old
 `save` method. this would make the implementation and the usage of the
 saving method more clear.

 what do you think?

 ---

 post transferred from https://github.com/rails/rails/issues/20662

 --
 You received this message because you are subscribed to the Google Groups
 Ruby on Rails: Core group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to rubyonrails-core+unsubscr...@googlegroups.com.
 To post to this group, send email to rubyonrails-core@googlegroups.com.
 Visit this group at http://groups.google.com/group/rubyonrails-core.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups Ruby 
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] update_columns doesn't support an empty hash

[Rafael Mendonça França]

Yes. It is raised by `update_all(attributes)`.

On Thu, May 7, 2015 at 3:19 PM Xavier Noria f...@hashref.com wrote:

 It makes sense to me, you get passed a hash with the attributes to update,
 which could be none.

 This is a no-op edge-case similar to append an empty list to a list, etc.,
 and could have use cases where the hash is built programatically.

 The implementation generally uses iterators, which is the normal way to
 support these edge-cases with no explicit handling, maybe the exception is
 raised by update_all(attributes)


 https://github.com/rails/rails/blob/master/activerecord/lib/active_record/persistence.rb#L312

 ?

  --
 You received this message because you are subscribed to the Google Groups
 Ruby on Rails: Core group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to rubyonrails-core+unsubscr...@googlegroups.com.
 To post to this group, send email to rubyonrails-core@googlegroups.com.
 Visit this group at http://groups.google.com/group/rubyonrails-core.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups Ruby 
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] update_columns doesn't support an empty hash

[Rafael Mendonça França]

This behavior was added at https://github.com/rails/rails/pull/7133.

Also don't assume that `update_attributes` and `update_columns` are
analogues. The later is dealing directly with the database without any kind
of interaction with the object instance, so they will behaves differently
in a lot of ways, like type casting for instance.

On Thu, May 7, 2015 at 2:52 PM Rafael Mendonça França 
rafaelmfra...@gmail.com wrote:

 And what happen if users expect N to be between 1 and many and we
 silently do nothing when 0 is sent to these methods?

 In my opinion if you don't have changes to be made in the database, just
 don't call the method.

 On Thu, May 7, 2015 at 2:47 PM Michael Mahemoff mahem...@gmail.com
 wrote:

 Bah I mean N is between 0 and many (rather than 1 and many).


 On Thursday, 7 May 2015 18:46:51 UTC+1, Michael Mahemoff wrote:

 Basically because http://en.wikipedia.org/wiki/Null_Object_pattern.
 It's often the case that systems have to deal with N possible changes,
 where N is between 0 and 1. e.g. I might have a procedure to gradually
 build up a list of things to change, starting with {} and appending to it
 if certain conditions are met. It wouldn't be an exceptional situation if
 none of those conditions are met.

 On Thursday, 7 May 2015 18:24:50 UTC+1, Rafael Mendonça França wrote:

 Are not both cases invalid input? Why should we accept empty hashes?

 On Thu, May 7, 2015 at 2:14 PM Michael Mahemoff mahe...@gmail.com
 wrote:

 The following will return an error:

  Post.first.update_columns({})
 ArgumentError: Empty list of attributes to change

 I think that's surprising, because I see update_columns as an analogue
 to update_attributes, just without callbacks happening. An empty hash for
 the latter is fine:

  Post.first.update_attributes({})
 true

 So shouldn't update_columns support an empty hash too? In the rare
 cases where callbacks should be avoided and this is needed, it would save
 having to make a special-case check to prevent the error.

 --
 You received this message because you are subscribed to the Google
 Groups Ruby on Rails: Core group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to rubyonrails-co...@googlegroups.com.
 To post to this group, send email to rubyonra...@googlegroups.com.
 Visit this group at http://groups.google.com/group/rubyonrails-core.
 For more options, visit https://groups.google.com/d/optout.

  --
 You received this message because you are subscribed to the Google Groups
 Ruby on Rails: Core group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to rubyonrails-core+unsubscr...@googlegroups.com.
 To post to this group, send email to rubyonrails-core@googlegroups.com.
 Visit this group at http://groups.google.com/group/rubyonrails-core.
 For more options, visit https://groups.google.com/d/optout.



-- 
You received this message because you are subscribed to the Google Groups Ruby 
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] update_columns doesn't support an empty hash

[Rafael Mendonça França]

And what happen if users expect N to be between 1 and many and we
silently do nothing when 0 is sent to these methods?

In my opinion if you don't have changes to be made in the database, just
don't call the method.

On Thu, May 7, 2015 at 2:47 PM Michael Mahemoff mahem...@gmail.com wrote:

 Bah I mean N is between 0 and many (rather than 1 and many).


 On Thursday, 7 May 2015 18:46:51 UTC+1, Michael Mahemoff wrote:

 Basically because http://en.wikipedia.org/wiki/Null_Object_pattern. It's
 often the case that systems have to deal with N possible changes, where N
 is between 0 and 1. e.g. I might have a procedure to gradually build up a
 list of things to change, starting with {} and appending to it if certain
 conditions are met. It wouldn't be an exceptional situation if none of
 those conditions are met.

 On Thursday, 7 May 2015 18:24:50 UTC+1, Rafael Mendonça França wrote:

 Are not both cases invalid input? Why should we accept empty hashes?

 On Thu, May 7, 2015 at 2:14 PM Michael Mahemoff mahe...@gmail.com
 wrote:

 The following will return an error:

  Post.first.update_columns({})
 ArgumentError: Empty list of attributes to change

 I think that's surprising, because I see update_columns as an analogue
 to update_attributes, just without callbacks happening. An empty hash for
 the latter is fine:

  Post.first.update_attributes({})
 true

 So shouldn't update_columns support an empty hash too? In the rare
 cases where callbacks should be avoided and this is needed, it would save
 having to make a special-case check to prevent the error.

 --
 You received this message because you are subscribed to the Google
 Groups Ruby on Rails: Core group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to rubyonrails-co...@googlegroups.com.
 To post to this group, send email to rubyonra...@googlegroups.com.
 Visit this group at http://groups.google.com/group/rubyonrails-core.
 For more options, visit https://groups.google.com/d/optout.

  --
 You received this message because you are subscribed to the Google Groups
 Ruby on Rails: Core group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to rubyonrails-core+unsubscr...@googlegroups.com.
 To post to this group, send email to rubyonrails-core@googlegroups.com.
 Visit this group at http://groups.google.com/group/rubyonrails-core.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups Ruby 
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] update_columns doesn't support an empty hash

[Rafael Mendonça França]

Are not both cases invalid input? Why should we accept empty hashes?

On Thu, May 7, 2015 at 2:14 PM Michael Mahemoff mahem...@gmail.com wrote:

 The following will return an error:

  Post.first.update_columns({})
 ArgumentError: Empty list of attributes to change

 I think that's surprising, because I see update_columns as an analogue to
 update_attributes, just without callbacks happening. An empty hash for the
 latter is fine:

  Post.first.update_attributes({})
 true

 So shouldn't update_columns support an empty hash too? In the rare cases
 where callbacks should be avoided and this is needed, it would save having
 to make a special-case check to prevent the error.

 --
 You received this message because you are subscribed to the Google Groups
 Ruby on Rails: Core group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to rubyonrails-core+unsubscr...@googlegroups.com.
 To post to this group, send email to rubyonrails-core@googlegroups.com.
 Visit this group at http://groups.google.com/group/rubyonrails-core.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups Ruby 
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] Addition of 'deep_assoc` method to Hash in core_ext

[Rafael Mendonça França]

I think we had this same request several times and we always rejected it.

I never had to use this pattern and I believe it may be a code smell, but
I'm not sure about your usage, so it would be great if you explain why you
have this pattern in your application and how often.

The reason that I'm asking that we are in a kind of code freeze of Active
Support core extension and we avoid the maximum to add new stuff there
unless it is really well justified common pattern or it will be used by the
framework itself.

I also recommend you to propose to Ruby itself, if we could get it accepted
in the language itself we can backport the feature inside Rails.

This is the process that we are even using for methods proposed by Core
team members. David proposed Object#itself and we also implemented it
inside Ruby 2.2. That way we were able to remove the Rails implementation
after we required only Ruby 2.2+.

On Thu, Apr 16, 2015 at 7:49 PM micahbuckleyfar...@gmail.com wrote:

 Hello,

 I wanted to see what people thought about adding a deep_assoc method to
 Hash in core_ext.

 Given a hash like this:
 hash = {a: {b: {c: :d}}}

 Its usage would look like this:
 hash.deep_assoc(:a, :b, :c)
 # = :d
 hash.deep_assoc(:a, :e, :f)
 # = nil

 It is basically a much cleaner way to avoid this pattern:
 hash.try(:[], :a).try(:[], :b).try(:[], :c)

 It is the one thing which I find myself continually missing in Hash.

 A basic implementation looks like this:

 class Hash
   def deep_assoc(*keys)
 current = keys.shift
 return self[current] if keys.empty?
 return nil unless self[current].is_a?(Hash)
 self[current].deep_assoc(keys)
   end
 end

 Please let me know your thoughts.

 Thanks!
 Micah Buckley-Farlee

 --
 You received this message because you are subscribed to the Google Groups
 Ruby on Rails: Core group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to rubyonrails-core+unsubscr...@googlegroups.com.
 To post to this group, send email to rubyonrails-core@googlegroups.com.
 Visit this group at http://groups.google.com/group/rubyonrails-core.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups Ruby 
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] [ANN] Rails 4.2.1 and 4.1.10 have been released!

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that after four release candidates the final versions
for Rails 4.2.1 and 4.1.10 have been released.

## CHANGES since 4.1.9

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.1.10/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.1.10/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v4.1.10/actionview/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.1.10/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.1.10/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.1.10/activesupport/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.1.10/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.1.9...v4.1.10).

## CHANGES since 4.2.0

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1/actionview/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1/activesupport/CHANGELOG.md)
* [Active Job CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1/activejob/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.2.0...v4.2.1).

## SHA-256

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-256 hashes.

Here are the checksums for 4.1.10:

```
$ shasum -a 256 *4.1.10*
4d771e1042dc40148f7d13e9776bd3df4d7a1f116c7991b33b3ee5ade2771edf
 actionmailer-4.1.10.gem
383fbbc9db04529b15765d4b3236980b8f0c7e050128a467c2dece76b9dea29e
 actionpack-4.1.10.gem
4c72eca866e4a80b3a56760aeb859e26bbe221fc2c06c13bc8d3220284900330
 actionview-4.1.10.gem
277d3fd1736ef1c4043592f482e6dea5cf4cc7d50c706b8be4971058a0df69cc
 activemodel-4.1.10.gem
a4ab57ff0183a630b46c2fb1c8700cc139f45808b81e4650d6f235102e3d9ae6
 activerecord-4.1.10.gem
b495b8490a7f3a885c8d0868858cca5070be41a5001642d2eb83a2f2e794082a
 activesupport-4.1.10.gem
9f81f8b716ba76ea768b1c0ed4a185a3f7647b384fc297c26c2b51be82856fd3
 rails-4.1.10.gem
55546f3c8e40c63cd7fd34b41dcf79eb302a38dd9b5a0383e60e9e747e7ecfe9
 railties-4.1.10.gem
```

Here are the checksums for 4.2.1:

```
$ shasum -a 256 *4.2.1*
f322b21623eb10eb302a21a803625bd57ce2b4ae24c2b5c14934a1359d63cf60
 actionmailer-4.2.1.gem
71fecb2c58b81dc97d9c8fe065004010cccd2a7acd1bc8a459d42b55c4882ca2
 actionpack-4.2.1.gem
cf7dbb0b5d7a9ccb9be1870be97e5ec319e3ee0f5dc766e62c20fafe92c02bd5
 actionview-4.2.1.gem
33cee3d50dbfacd105766be1f5885dfa614deb8a18c45a3a398f294457c8bd63
 activejob-4.2.1.gem
c55157de170de2c10ad2755c3fa434e7adcbe34af2526b4cf20b63feb5f8169b
 activemodel-4.2.1.gem
5febff6cb42c0fb94bb7708ad7df7f9ef6d365a27ef35c239674d651013c6cf2
 activerecord-4.2.1.gem
36742443adbc7b4648b8674d119ac9dc446c3a555ce73a5a28b1fa029e8adad4
 activesupport-4.2.1.gem
6b5f7d3a4a9eb2f181bab4a657315dbe08d0be218eae6017bef8a45dede211cb
 rails-4.2.1.gem
a01ce5513806d712cca8ed60429493d18093eff680201e2e288602c1405e2e8b
 railties-4.2.1.gem
```

I'd like to thank you all, every contributor who helped with this release.

-- 
You received this message because you are subscribed to the Google Groups Ruby 
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] Rename transactional fixtures to something clearer and more descriptive

[Rafael Mendonça França]

Seems good to me.

On Fri, Mar 6, 2015 at 4:04 AM Brandon Weiss bran...@anti-pattern.com
wrote:

 I think the name transactional fixtures is a little misleading and
 confusing, because (as far as I can tell) it doesn't really have anything
 to do with fixtures.

 This is pretty embarrassing, but I've been using Rails almost since 1.0
 and I had no idea that transactional fixtures were running on my tests. I
 don't use fixtures so I just erroneously assumed that feature didn't work
 for me. I've been using Database Cleaner unnecessarily for like the last
 four years. I know, it seems ridiculous, but I talked to a few other fairly
 savvy Rails users and they had no idea either. I'm beginning to think my
 misunderstanding is fairly common.

 Is there any interest in renaming the feature to something clearer and
 more descriptive, like transactional tests? E.g. use_transactional_tests.
 If so, I'd be happy to do the work to deprecate the old name, add the new
 name, and rename/update everything where necessary.

 --
 You received this message because you are subscribed to the Google Groups
 Ruby on Rails: Core group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to rubyonrails-core+unsubscr...@googlegroups.com.
 To post to this group, send email to rubyonrails-core@googlegroups.com.
 Visit this group at http://groups.google.com/group/rubyonrails-core.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups Ruby 
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] [ANN] Rails 4.2.1.rc3 and 4.1.10.rc3 have been released!

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 4.2.1.rc3 and 4.1.10.rc3 have been
released.

There were found some regressions in the last release candidates so,
following release process we are
releasing new release candidates.

If no regressions are found expect the final release this Thursday, on
March 5, 2015.
If you find one, please open an [issue on GitHub](
https://github.com/rails/rails/issues/new)
and mention me (@rafaelfranca) on it, so that we can fix it before the
final release.

## CHANGES since 4.1.9

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.1.10.rc3/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.1.10.rc3/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v4.1.10.rc3/actionview/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.1.10.rc3/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.1.10.rc3/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.1.10.rc3/activesupport/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.1.10.rc3/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.1.9...v4.1.10.rc3).

## CHANGES since 4.2.0

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1.rc3/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1.rc3/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1.rc3/actionview/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1.rc3/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1.rc3/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1.rc3/activesupport/CHANGELOG.md)
* [Active Job CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1.rc3/activejob/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1.rc3/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.2.0...v4.2.1.rc3).

## SHA-1

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-1 hashes.

Here are the checksums for 4.1.10.rc3:

```
$ shasum -a 256 *4.1.10.rc3*
3fdef2245e3d1cbd23403e319e90504de5a6d9c1d3882520555d5474888e64e8
 actionmailer-4.1.10.rc3.gem
b6ee8ce93aeb4e1c3698b5d181997a6cfd903df4ee5ad4ff006ba1e8e4f9cbeb
 actionpack-4.1.10.rc3.gem
855a02aa85d9df389ee401d9374ba1b6de97302bfa5b16cc3461b2068f2bac8c
 actionview-4.1.10.rc3.gem
1f255ba5894e9c4ba62ff1362eefb5d4f69341e1b6633f34f5a74f3e5f50abe7
 activemodel-4.1.10.rc3.gem
ae172a7ad49fe1aa007f99d33c9365f4027f7460aa20b3f2c4e699a029894e9f
 activerecord-4.1.10.rc3.gem
efc14fb6fb046314e770f39702cebae5108abfe8a2f972baf503354b4d8962f6
 activesupport-4.1.10.rc3.gem
6958130cadf8306732bd0ef09a49f689c85e8f675aa77392c2bff605dc6fe795
 rails-4.1.10.rc3.gem
056ae92c2c280c30683bff33840b580dd95a4f6d6a76d760f82dc48d84a39862
 railties-4.1.10.rc3.gem
```

Here are the checksums for 4.2.1.rc3:

```
$ shasum -a 256 *4.2.1.rc3*
7290338a93cb8d1552aca33b09a8bc00e7774f0110fc1e28af0b495cbd393f24
 actionmailer-4.2.1.rc3.gem
9838985eb38550060d4220a9015ca983df1c87c8d059f8943c52db721f2fb7d3
 actionpack-4.2.1.rc3.gem
a9af6c312c869ddae79a220c5179d0d80f4fab397115976287a5877d2f80dea2
 actionview-4.2.1.rc3.gem
922c47a84ffb1bfde8bc2e3fb18f2e19bb61c8326428c31c09be56296ce6a63b
 activejob-4.2.1.rc3.gem
1183c5e4f8c2d608b1d7b774a1720c7595359356c77b495880acf79d22ae0865
 activemodel-4.2.1.rc3.gem
7976ea67cd5f7193247751bb6300990d3c5ba9eb74c5ea0c4b382e776a23889e
 activerecord-4.2.1.rc3.gem
69704869beccae0694ba5f1e9179eaaa60b99b19adc9a48e890fe1b573894a82
 activesupport-4.2.1.rc3.gem
90043b5ce4c1191e62a0c5b6bc4580553a540d7e6d18c7975de180fe8af61462
 rails-4.2.1.rc3.gem
a72254f18ab76fca24f3a478779aa34f41a5bf89f71a8fe16f1945f991f0b10f
 railties-4.2.1.rc3.gem
```

I'd like to thank you all, every contributor who helped with this release.

-- 
You received this message because you are subscribed to the Google Groups Ruby 
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] [ANN] Rails 4.2.1.rc2 and 4.1.10.rc2 have been released!

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 4.2.1.rc2 and 4.1.10.rc2 have been
released.

There were found some regressions in the last release candidates so,
following release process we are
releasing new release candidates.

If no regressions are found expect the final release this Monday, on March
2, 2015.
If you find one, please open an [issue on GitHub](
https://github.com/rails/rails/issues/new)
and mention me (@rafaelfranca) on it, so that we can fix it before the
final release.

## CHANGES since 4.1.9

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.1.10.rc2/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.1.10.rc2/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v4.1.10.rc2/actionview/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.1.10.rc2/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.1.10.rc2/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.1.10.rc2/activesupport/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.1.10.rc2/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.1.9...v4.1.10.rc2).

## CHANGES since 4.2.0

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1.rc2/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1.rc2/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1.rc2/actionview/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1.rc2/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1.rc2/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1.rc2/activesupport/CHANGELOG.md)
* [Active Job CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1.rc2/activejob/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1.rc2/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.2.0...v4.2.1.rc2).

## SHA-1

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-1 hashes.

Here are the checksums for 4.1.10.rc2:

```
$ shasum *4.1.10.rc2*
2ac66bc18099e97e91433dd2a16610840adbe229  actionmailer-4.1.10.rc2.gem
7af1a70d5436936df7602ce25b8607dd657d26fd  actionpack-4.1.10.rc2.gem
25f87be1c36551583c5bdc3034731ab9d327e650  actionview-4.1.10.rc2.gem
61eddccaa119592a8fa3424e33af26f3c52afd87  activemodel-4.1.10.rc2.gem
30bd5d356e704f9122f51d0503a3d57bd4b7c456  activerecord-4.1.10.rc2.gem
1da6fd1c9f6a5bebf743ddbc13d25c54293baf5a  activesupport-4.1.10.rc2.gem
7c42be6e6a7f059dcad390f0d690aff842138870  rails-4.1.10.rc2.gem
3f036bc1450f4e784ee0ce8118f057f68e56422d  railties-4.1.10.rc2.gem
```

Here are the checksums for 4.2.1.rc2:

```
$ shasum *4.2.1.rc2*
af8d52587a348ea70e9b6a751207a9a6aa4044f3  actionmailer-4.2.1.rc2.gem
ab218bb9396357b48027e1512544cfb3188ec3bd  actionpack-4.2.1.rc2.gem
5315fd389885775fc03863146704aab37333e0c8  actionview-4.2.1.rc2.gem
15c11c2aff82876241a3a9ff90b00dfb6d834fa2  activejob-4.2.1.rc2.gem
f700c318378a8e3292b23c9495e68bc49f9a1ef1  activemodel-4.2.1.rc2.gem
dc91f9e52b8fd9ab0fac294f13ab7f9425cb0a67  activerecord-4.2.1.rc2.gem
ab95e792e93392605985469b3ec0546d3917c63c  activesupport-4.2.1.rc2.gem
af242d941255666ce08a51813898fe8c29bb613d  rails-4.2.1.rc2.gem
c0e72712484fdc821d6a0f08504318e075feba83  railties-4.2.1.rc2.gem

```

I'd like to thank you all, every contributor who helped with this release.

-- 
You received this message because you are subscribed to the Google Groups Ruby 
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] [ANN] Rails 4.2.1.rc1 and 4.1.10.rc1 have been released!

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 4.2.1.rc1 and 4.1.10.rc1 have been
released.

If no regressions are found expect the final release this Wednesday, on
February 25, 2015.
If you find one, please open an [issue on GitHub](
https://github.com/rails/rails/issues/new)
and mention me (@rafaelfranca) on it, so that we can fix it before the
final release.

## CHANGES since 4.1.9

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.1.10.rc1/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.1.10.rc1/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v4.1.10.rc1/actionview/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.1.10.rc1/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.1.10.rc1/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.1.10.rc1/activesupport/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.1.10.rc1/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.1.9...v4.1.10.rc1).

## CHANGES since 4.2.0

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1.rc1/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1.rc1/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1.rc1/actionview/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1.rc1/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1.rc1/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1.rc1/activesupport/CHANGELOG.md)
* [Active Job CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1.rc1/activejob/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.2.1.rc1/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.2.0...v4.2.1.rc1).

## SHA-1

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-1 hashes.

Here are the checksums for 4.1.10.rc1:

```
$ shasum *4.1.10.rc1*
173663408f82f4f6b718d0493ccd7372b1ebb04b  actionmailer-4.1.10.rc1.gem
e2f2239ba08498b0222c73d749ce1fc0b80227ce  actionpack-4.1.10.rc1.gem
3ea60b85b2c6d9c6dd517f19cca6d4184f168c3e  actionview-4.1.10.rc1.gem
fad32c6fa623c848c59c7ec4ea6f95bbe55c800e  activemodel-4.1.10.rc1.gem
5fa2bbfc017cd5000d5a05923b0ed00eaf0763d2  activerecord-4.1.10.rc1.gem
593986a562d2967690def2acfb4f3807b749c8d5  activesupport-4.1.10.rc1.gem
9b3243b73e8094bdef92a9a3fe8e13c59660fcb8  rails-4.1.10.rc1.gem
629269e65fb4b2eaacf3341060b06a6857479ec8  railties-4.1.10.rc1.gem
```

Here are the checksums for 4.2.1.rc1:

```
$ shasum *4.2.1.rc1*
7540e2101c574c1b28428d25b26e2840bd811b07  actionmailer-4.2.1.rc1.gem
2256120417e0a2c554fa622f59bfce672c565df2  actionpack-4.2.1.rc1.gem
6add23517bf1c2cdc29b04e5634305c0b5bcc496  actionview-4.2.1.rc1.gem
894a9419a70e6061e07ab2c23f75f0c5fd886b10  activejob-4.2.1.rc1.gem
c268d0711889e2df9991a80f1e01180573b79f9f  activemodel-4.2.1.rc1.gem
39ca67053e52260954876fbf385e260b56c870b9  activerecord-4.2.1.rc1.gem
a937629fed3f6ddeb9f939273dd5e7955a7f25a1  activesupport-4.2.1.rc1.gem
773cce2bacede08390bf9488665d03af33995271  rails-4.2.1.rc1.gem
703b959222cd0466a244cca5bd322de9fb7b76a6  railties-4.2.1.rc1.gem
```

I'd like to thank you all, every contributor who helped with this release.

-- 
You received this message because you are subscribed to the Google Groups Ruby 
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] .html_safe is ambiguous and should be renamed

[Rafael Mendonça França]

Renaming this method is not an option.

The main reason is: it should not be used by end users. It is an
implementation detail of the framework and although it is exposed to the
users we don't recommend to use it directly.

So when Andrew said we should rename it to something even longer so that
people don't use it it was a joke, but just a half joke. We really don't
want to people to use it.

Almost 90% of the cases that people use `html_safe` what they really wanted
is `sanitize`. Also, some day HTML escaping implementation could change
`html_safe` be completely gone.

This is why we have the `raw` method, to expose a public API to disable the
HTML escaping without exposing the implementation detail.

So I don't think we should rename an internal method to make it explicit
to end users.

On Fri Feb 06 2015 at 1:41:36 PM Ufuk Kayserilioglu u...@paralaus.com
wrote:

 IMHO, the target audience is largely an irrelevant concern. The more
 important concept is making users fall into the pit
 http://blog.codinghorror.com/falling-into-the-pit-of-success/ of success
 http://blogs.msdn.com/b/brada/archive/2003/10/02/50420.aspx. In that
 light, the proposed renaming makes sense.

 Don't forget, the clearer the intention of the method the better it is for
 both novice and experienced programmers.

 --
 Ufuk Kayserilioglu


 On 6 February 2015 at 17:24:17, Nicolas Cavigneaux (n...@bounga.org)
 wrote:

 Le 6 févr. 2015 à 16:21, Jason Fleetwood-Boldt a écrit :

 
  Is Rails' API coded for the neophyte or the experienced dev?
 
  The eternal question.

 For people who know how to read basic, essential doc and well documented
 stuff?

 --
 Nicolas Cavigneaux
 www.bounga.org
 www.cavigneaux.net





 --
 You received this message because you are subscribed to the Google Groups
 Ruby on Rails: Core group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to rubyonrails-core+unsubscr...@googlegroups.com.
 To post to this group, send email to rubyonrails-core@googlegroups.com.
 Visit this group at http://groups.google.com/group/rubyonrails-core.
 For more options, visit https://groups.google.com/d/optout.

 --
 You received this message because you are subscribed to the Google Groups
 Ruby on Rails: Core group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to rubyonrails-core+unsubscr...@googlegroups.com.
 To post to this group, send email to rubyonrails-core@googlegroups.com.
 Visit this group at http://groups.google.com/group/rubyonrails-core.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups Ruby 
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] .html_safe is ambiguous and should be renamed

[Rafael Mendonça França]

Yeah. This is one of the example of things that were supposed to be
implementation detail and became a widely used method, just like
`arel_table`. It is not that you can't use it at all, but that you should
be very careful when using it. Like I said almost 90% of its usages can be
avoided using `sanitize` or the proper tag helpers.

I agree we should improve the education about this subject.

On Fri Feb 06 2015 at 2:02:20 PM George Millo georgejulianmi...@gmail.com
wrote:

 I didn't realise I wasn't supposed to be using html_safe. Perhaps the
 documentation should be updated to make this clearer?

 On 6 February 2015 at 16:50, Rafael Mendonça França 
 rafaelmfra...@gmail.com wrote:

 Renaming this method is not an option.

 The main reason is: it should not be used by end users. It is an
 implementation detail of the framework and although it is exposed to the
 users we don't recommend to use it directly.

 So when Andrew said we should rename it to something even longer so
 that people don't use it it was a joke, but just a half joke. We really
 don't want to people to use it.

 Almost 90% of the cases that people use `html_safe` what they really
 wanted is `sanitize`. Also, some day HTML escaping implementation could
 change `html_safe` be completely gone.

 This is why we have the `raw` method, to expose a public API to disable
 the HTML escaping without exposing the implementation detail.

 So I don't think we should rename an internal method to make it
 explicit to end users.


 On Fri Feb 06 2015 at 1:41:36 PM Ufuk Kayserilioglu u...@paralaus.com
 wrote:

 IMHO, the target audience is largely an irrelevant concern. The more
 important concept is making users fall into the pit
 http://blog.codinghorror.com/falling-into-the-pit-of-success/ of
 success http://blogs.msdn.com/b/brada/archive/2003/10/02/50420.aspx.
 In that light, the proposed renaming makes sense.

 Don't forget, the clearer the intention of the method the better it is
 for both novice and experienced programmers.

 --
 Ufuk Kayserilioglu


 On 6 February 2015 at 17:24:17, Nicolas Cavigneaux (n...@bounga.org)
 wrote:

 Le 6 févr. 2015 à 16:21, Jason Fleetwood-Boldt a écrit :

 
  Is Rails' API coded for the neophyte or the experienced dev?
 
  The eternal question.

 For people who know how to read basic, essential doc and well documented
 stuff?

 --
 Nicolas Cavigneaux
 www.bounga.org
 www.cavigneaux.net





 --
 You received this message because you are subscribed to the Google
 Groups Ruby on Rails: Core group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to rubyonrails-core+unsubscr...@googlegroups.com.
 To post to this group, send email to rubyonrails-core@googlegroups.com.
 Visit this group at http://groups.google.com/group/rubyonrails-core.
 For more options, visit https://groups.google.com/d/optout.

 --
 You received this message because you are subscribed to the Google
 Groups Ruby on Rails: Core group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to rubyonrails-core+unsubscr...@googlegroups.com.
 To post to this group, send email to rubyonrails-core@googlegroups.com.
 Visit this group at http://groups.google.com/group/rubyonrails-core.
 For more options, visit https://groups.google.com/d/optout.

  --

 You received this message because you are subscribed to a topic in the
 Google Groups Ruby on Rails: Core group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/rubyonrails-core/T9N5wexIg80/unsubscribe
 .
 To unsubscribe from this group and all its topics, send an email to
 rubyonrails-core+unsubscr...@googlegroups.com.


 To post to this group, send email to rubyonrails-core@googlegroups.com.
 Visit this group at http://groups.google.com/group/rubyonrails-core.
 For more options, visit https://groups.google.com/d/optout.

  --
 You received this message because you are subscribed to the Google Groups
 Ruby on Rails: Core group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to rubyonrails-core+unsubscr...@googlegroups.com.
 To post to this group, send email to rubyonrails-core@googlegroups.com.
 Visit this group at http://groups.google.com/group/rubyonrails-core.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups Ruby 
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] .html_safe is ambiguous and should be renamed

[Rafael Mendonça França]

In our opinion this is will cause an unnecessary amount of work to people
upgrading their applications. We want to avoid adding breaking
changes/deprecation if we can.

On Fri Feb 06 2015 at 2:10:33 PM Ufuk Kayserilioglu u...@paralaus.com
wrote:

 Rafael,

 I do agree with you; however, the same argument could be made for renaming
 it as well. If it is a private implementation concern and nobody should be
 using it, then there should be no problems with a rename to make sure that
 the name is scary enough to stop people from using it and/or break
 applications that are using it.

 --
 Ufuk Kayserilioglu


 On 6 February 2015 at 17:50:24, Rafael Mendonça França (
 rafaelmfra...@gmail.com) wrote:
  Renaming this method is not an option.

 The main reason is: it should not be used by end users. It is an
 implementation detail of the framework and although it is exposed to the
 users we don't recommend to use it directly.

 So when Andrew said we should rename it to something even longer so that
 people don't use it it was a joke, but just a half joke. We really don't
 want to people to use it.

  Almost 90% of the cases that people use `html_safe` what they really
 wanted is `sanitize`. Also, some day HTML escaping implementation could
 change `html_safe` be completely gone.

  This is why we have the `raw` method, to expose a public API to disable
 the HTML escaping without exposing the implementation detail.

  So I don't think we should rename an internal method to make it
 explicit to end users.

 On Fri Feb 06 2015 at 1:41:36 PM Ufuk Kayserilioglu u...@paralaus.com
 wrote:

  IMHO, the target audience is largely an irrelevant concern. The more
 important concept is making users fall into the pit
 http://blog.codinghorror.com/falling-into-the-pit-of-success/ of
 success http://blogs.msdn.com/b/brada/archive/2003/10/02/50420.aspx.
 In that light, the proposed renaming makes sense.

  Don't forget, the clearer the intention of the method the better it is
 for both novice and experienced programmers.

 --
 Ufuk Kayserilioglu


 On 6 February 2015 at 17:24:17, Nicolas Cavigneaux (n...@bounga.org)
 wrote:

 Le 6 févr. 2015 à 16:21, Jason Fleetwood-Boldt a écrit :

 
  Is Rails' API coded for the neophyte or the experienced dev?
 
  The eternal question.

 For people who know how to read basic, essential doc and well documented
 stuff?

 --
 Nicolas Cavigneaux
 www.bounga.org
 www.cavigneaux.net





 --
 You received this message because you are subscribed to the Google Groups
 Ruby on Rails: Core group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to rubyonrails-core+unsubscr...@googlegroups.com.
 To post to this group, send email to rubyonrails-core@googlegroups.com.
 Visit this group at http://groups.google.com/group/rubyonrails-core.
 For more options, visit https://groups.google.com/d/optout.
  --
 You received this message because you are subscribed to the Google Groups
 Ruby on Rails: Core group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to rubyonrails-core+unsubscr...@googlegroups.com.
 To post to this group, send email to rubyonrails-core@googlegroups.com.
 Visit this group at http://groups.google.com/group/rubyonrails-core.
 For more options, visit https://groups.google.com/d/optout.

  --
 You received this message because you are subscribed to the Google Groups
 Ruby on Rails: Core group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to rubyonrails-core+unsubscr...@googlegroups.com.
 To post to this group, send email to rubyonrails-core@googlegroups.com.
 Visit this group at http://groups.google.com/group/rubyonrails-core.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups Ruby 
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] [ANN] Rails 4.1.9 and 4.0.13 have been released!

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 4.1.9 and 4.0.13 have been released.

This will be also the last release of 4.0 series as announced
[in a previous blog post](
http://weblog.rubyonrails.org/2014/9/12/Rails-4-1-6-and-4-0-10-has-been-released/
).

As per our maintenance policy, the release of Rails 4.2.0 means bug fixes
will only apply to 4-2-stable,
regular security issues to 4.2.x, 4.1.x, and severe security issues to
4.2.x, 4.1.x, and 3.2.x.
In addition to these already stated commitments, I agreed to also apply bug
fixes to 4-1-stable
until the Rails 5 release.

As before, we will announce in a future blog post when we will drop bug
fixes support
for Rails 4.1.

## CHANGES since 4.0.12

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.0.13/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.0.13/actionpack/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.0.13/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.0.13/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.0.13/activesupport/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.0.13/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.0.12...v4.0.13).

## CHANGES since 4.1.8

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.1.9/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.1.9/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v4.1.9/actionview/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.1.9/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.1.9/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.1.9/activesupport/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.1.9/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.1.8...v4.1.9).

## SHA-1

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-1 hashes.

Here are the checksums for 4.0.13:

```
$ shasum *4.0.13*
75f128ffb5813f6ec895a2f6c000a18531232bfb  actionmailer-4.0.13.gem
7356b2d90904ea3e5854a5fd5c969ff5521ee6bf  actionpack-4.0.13.gem
019bc6e77c2c430e52d93642bee8ad137ec288d8  activemodel-4.0.13.gem
fb367963994f153f68b904b8508b215b60a6a0ca  activerecord-4.0.13.gem
55cbd61d330d29fac50249d5ab9964e34a102f44  activesupport-4.0.13.gem
e4d679c792f0a2faafe69fd87217320bc318fc03  rails-4.0.13.gem
856d1f60df48479c4faba3de6d3ffcfadeee2f6b  railties-4.0.13.gem
```

Here are the checksums for 4.1.9:

```
$ shasum *4.1.9*
7d4a8ce21aa0429ec5fc05c64e2f64fa769a1c4a  actionmailer-4.1.9.gem
37b3990b77669877ab675124662ca5c0e880e556  actionpack-4.1.9.gem
baf6c54a9f411e9399dc7f9ad99aaa892a43293a  actionview-4.1.9.gem
cd9c214923ea0094fb65825b1866c3bc5b80fbdb  activemodel-4.1.9.gem
330a753ec001e38834406c464e306c3c43e276b5  activerecord-4.1.9.gem
66904e1371b047348d0247c43b9f1c3c596671bf  activesupport-4.1.9.gem
12a8b208566f4c822cc9199f51f60fd8baf010bc  rails-4.1.9.gem
2c494849ac54b8b3238d23fe62c81da37ca08e1b  railties-4.1.9.gem
```

I'd like to thank you all, every contributor who helped with this release.

-- 
You received this message because you are subscribed to the Google Groups Ruby 
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

[Rails-core] [ANN] Rails 4.1.9.rc1 and 4.0.13.rc1 have been released!

[Rafael Mendonça França]

Hi everyone,

I am happy to announce that Rails 4.1.9.rc1 and 4.0.13.rc1 have been
released.

This is the first release of the year and it includes a lot of bug fixes.
This will be also
the last release of 4.0 series as announced
[in a previous blog post](
http://weblog.rubyonrails.org/2014/9/12/Rails-4-1-6-and-4-0-10-has-been-released/
).

As per our maintenance policy, the release of Rails 4.2.0 means bug fixes
will only apply to 4-2-stable,
regular security issues to 4.2.x, 4.1.x, and severe security issues to
4.2.x, 4.1.x, and 3.2.x.
In addition to these already stated commitments, I agreed to also apply bug
fixes to 4-1-stable
until the Rails 5 release.

As before, we will announce in a future blog post when we will drop bug
fixes support
for Rails 4.1.

If no regressions are found expect the final release this Tuesday, on
January 6, 2015.
If you find one, please open an [issue on GitHub](
https://github.com/rails/rails/issues/new)
and mention me (@rafaelfranca) on it, so that we can fix it before the
final release.

## CHANGES since 4.0.12

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.0.13.rc1/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.0.13.rc1/actionpack/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.0.13.rc1/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.0.13.rc1/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.0.13.rc1/activesupport/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.0.13.rc1/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.0.12...v4.0.13.rc1).

## CHANGES since 4.1.8

To view the changes for each gem, please read the changelogs on GitHub:

* [Action Mailer CHANGELOG](
https://github.com/rails/rails/blob/v4.1.9.rc1/actionmailer/CHANGELOG.md)
* [Action Pack CHANGELOG](
https://github.com/rails/rails/blob/v4.1.9.rc1/actionpack/CHANGELOG.md)
* [Action View CHANGELOG](
https://github.com/rails/rails/blob/v4.1.9.rc1/actionview/CHANGELOG.md)
* [Active Model CHANGELOG](
https://github.com/rails/rails/blob/v4.1.9.rc1/activemodel/CHANGELOG.md)
* [Active Record CHANGELOG](
https://github.com/rails/rails/blob/v4.1.9.rc1/activerecord/CHANGELOG.md)
* [Active Support CHANGELOG](
https://github.com/rails/rails/blob/v4.1.9.rc1/activesupport/CHANGELOG.md)
* [Railties CHANGELOG](
https://github.com/rails/rails/blob/v4.1.9.rc1/railties/CHANGELOG.md)

*Full listing*

To see the full list of changes, [check out all the commits on
GitHub](https://github.com/rails/rails/compare/v4.1.8...v4.1.9.rc1).

## SHA-1

If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-1 hashes.

Here are the checksums for 4.0.13.rc1:

```
$ shasum *4.0.13.rc1*
bf4ddb5aa6eefc6e2495a1364974a5b396d94596  actionmailer-4.0.13.rc1.gem
2bf785e91159bba8fe324e2f48a72277f2b3cf33  actionpack-4.0.13.rc1.gem
f9d92979e211ce7fa71252cf1b6b4ac94c7f0b91  activemodel-4.0.13.rc1.gem
d5147f64e08a3f5aed4c22ff1ebf640ca6fc0ae3  activerecord-4.0.13.rc1.gem
e6f1421262fd1064e973f3d2628c6129b4c20d17  activesupport-4.0.13.rc1.gem
f7416fc8485bb8a622fb50e0dd2c3fa5ca4215fa  rails-4.0.13.rc1.gem
8a0690bab5e43712e8e982fe02bf76ea989f9356  railties-4.0.13.rc1.gem
```

Here are the checksums for 4.1.9.rc1:

```
$ shasum *4.1.9.rc1*
8afbb9c71a8f6e0dff26daacde407fe35aac8375  actionmailer-4.1.9.rc1.gem
a5fd439bc41844a3c02671d7425bfa71d96cfbf1  actionpack-4.1.9.rc1.gem
a77aaa2f936445211e7455b3228a9bfe8f27a4ac  actionview-4.1.9.rc1.gem
65a7acbf9ef9b47392a48ab4c9ace44f12ea1f60  activemodel-4.1.9.rc1.gem
eb66d5c52f0740114de46e1a1b76a0079c723d1f  activerecord-4.1.9.rc1.gem
e758d54d7fabc7d23ff995646096f40d28df42a9  activesupport-4.1.9.rc1.gem
479a31dd8d9eea3de6f444139eaefc830c6db170  rails-4.1.9.rc1.gem
dae65c526ec8ee3abab9a9e8807ad7b210b7941d  railties-4.1.9.rc1.gem
```

I'd like to thank you all, every contributor who helped with this release.

Happy new year! :tada:

-- 
You received this message because you are subscribed to the Google Groups Ruby 
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.

Re: [Rails-core] Making FormBuilder#select work better with ActiveRecord collections

[Rafael Mendonça França]

Does not the collection_select work o this way? I know it has a
label_method that you can pass name to get the same behavior, and if I'm
not wrong disabled can accept a proc.

-- 
You received this message because you are subscribed to the Google Groups Ruby 
on Rails: Core group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-core+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-core@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyonrails-core.
For more options, visit https://groups.google.com/d/optout.