- 04 11月, 2012 2 次提交
-
-
由 Santiago Pastorino 提交于
-
由 Santiago Pastorino 提交于
-
- 01 11月, 2012 2 次提交
-
-
由 Arun Agrawal 提交于
-
由 Steve Klabnik 提交于
Fixes #8025
-
- 30 10月, 2012 1 次提交
-
-
由 Alexey Gaziev 提交于
-
- 29 10月, 2012 4 次提交
-
-
由 Nikita Afanasenko 提交于
It's sometimes hard to quickly find where deprecated call was performed, especially in case of migrating between Rails versions. So this is an attempt to improve the call stack part of the warning message by providing caller explicitly.
-
由 Carlos Antonio da Silva 提交于
-
由 Rafael Mendonça França 提交于
-
由 Rafael Mendonça França 提交于
Should not eager_load app/assets Conflicts: railties/CHANGELOG.md
-
- 28 10月, 2012 1 次提交
-
-
由 Rafael Mendonça França 提交于
-
- 27 10月, 2012 1 次提交
-
-
由 Jeremy Kemper 提交于
-
- 23 10月, 2012 1 次提交
-
-
由 Tima Maslyuchenko 提交于
-
- 22 10月, 2012 1 次提交
-
-
由 Geoffrey Roguelon 提交于
-
- 20 10月, 2012 1 次提交
-
-
由 Rafael Mendonça França 提交于
-
- 19 10月, 2012 4 次提交
-
-
由 Robb Shecter 提交于
-
由 Rafael Mendonça França 提交于
-
由 Rafael Mendonça França 提交于
Setting the action_dispatch.rack_cache options to true or a hash should be the way to enable it.
-
由 Rafael Mendonça França 提交于
-
- 18 10月, 2012 2 次提交
-
-
由 Rafael Mendonça França 提交于
-
由 Joshua Peek 提交于
-
- 17 10月, 2012 1 次提交
-
-
由 Joshua Peek 提交于
-
- 16 10月, 2012 3 次提交
-
-
由 AvnerCohen 提交于
-
由 Joshua Peek 提交于
-
由 Joshua Peek 提交于
-
- 15 10月, 2012 5 次提交
-
-
由 Joshua Peek 提交于
-
由 Joshua Peek 提交于
-
由 AvnerCohen 提交于
-
由 Jeremy Kemper 提交于
-
由 Robin Dupret 提交于
-
- 14 10月, 2012 1 次提交
-
-
由 Jeremy Kemper 提交于
-
- 13 10月, 2012 6 次提交
-
-
由 Jeremy Kemper 提交于
-
由 Jeremy Kemper 提交于
-
由 Jeremy Kemper 提交于
Remove the queue container. Premature consolidation. Set up and maintain queues in the classes that use them instead.
-
由 schneems 提交于
Developers from all levels will accidentally run rake tasks using the `rails` keyword when they meant to use `rake`. Often times beginners struggle with the difference between the tools. The most common example would be `$ rails db:migrate` Rather than telling the developer simply that they did not use a valid rails command, we can see if it was a valid rake command first. If it is a valid rake command we can auto execute it giving the user a period of time to cancel if that isn't what they intended. Here is what `rake db:migrate` would look like if you cancel the command: ```sh $ rails db:migrate Assuming you meant: $ rake db:migrate press any key to cancel in 3 seconds > command terminated ... ``` Here is what it looks like if you don't cancel the command: ```sh $ rails db:migrate Assuming you meant: $ rake db:migrate press any key to cancel in 3 seconds > Running: $ rake db:migrate == Foo: migrating ============================================================ == Foo: migrated (0.0000s) =================================================== ```
-
由 Rafael Mendonça França 提交于
Now we are using teh SynchronousQueue in the test environment instead of the TestQueue
-
由 Rafael Mendonça França 提交于
-
- 12 10月, 2012 2 次提交
-
-
由 Brent J. Nordquist 提交于
-
由 Jeremy Kemper 提交于
Immediately run queued jobs in tests. Otherwise you have to explicitly drain the queue to actually deliver your emails.
-
- 11 10月, 2012 2 次提交
-
-
由 Arun Agrawal 提交于
as it's removed here 1fc79546
-
由 Vijay Dev 提交于
Build failed with an error "invalid multibyte char (US-ASCII)" in these files. Apparently, some UTF-8 char disguised as whitespace causes this. Thanks @rafaelfranca
-