aboutsummaryrefslogtreecommitdiffstats
path: root/railties
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #8169 from nicolasdespres/robust_git_repository_checkRafael Mendonça França2012-11-133-1/+32
|\ | | | | Rake test:uncommitted finds git directory in ancestors.
| * Add ChangeLog entry.Nicolas Despres2012-11-131-0/+2
| |
| * Rake test:uncommitted finds git directory in ancestors.Nicolas Despres2012-11-102-1/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | Sometimes your git directory is an ancestor of your application root directory. For example: ./repo/.git/ ./repo/app/Rakefile In this case rake test:uncommitted will be unable to detect your SCM. This patch fixes this and add a test.
* | Removing warning : ambiguous first argumentArun Agrawal2012-11-111-2/+2
|/
* Removing warning : assigned but unused variableArun Agrawal2012-11-102-2/+2
|
* make the extremely useful logs debug levelAaron Patterson2012-11-091-2/+2
|
* copy the log level from the config settingsAaron Patterson2012-11-091-0/+1
|
* Clean up gemspecsVinny Diehl2012-11-081-14/+17
| | | | | | | | | | Organized the gemspec files a bit. * Made quotes more consistent (single quotes dominated, so I used that). * Moved license line down a line, separating it logically, and removed the extra whitespace before its = operator. * Minor whitespace fixes.
* `plugin new` adds dummy app tasks when necessary.Yves Senn2012-11-084-3/+18
| | | | | | | Closes #8121 The `plugin new` generator always adds the dummy app rake tasks, when a dummy app was created.
* Remove some line breaks between array items that make the assert file tests ↵Carlos Antonio da Silva2012-11-044-42/+19
| | | | harder to read
* Small change to remove warning unused variable.Arun Agrawal2012-11-011-1/+1
|
* Make sure that RAILS_ENV is set when accessing Rails.envSteve Klabnik2012-10-312-1/+6
| | | | Fixes #8025
* Make caller attribute in deprecation methods optionalAlexey Gaziev2012-10-301-3/+2
|
* Merge pull request #8063 from nikitug/deprecation_caller_contextCarlos Antonio da Silva2012-10-291-3/+4
|\ | | | | Provide a call stack for deprecation warnings where needed.
| * Provide a call stack for deprecation warnings where needed.Nikita Afanasenko2012-10-291-3/+4
| | | | | | | | 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.
* | Fix deprecation message in test for Path#childrenCarlos Antonio da Silva2012-10-291-1/+1
|/
* Add test to deprecation of Path#childrenRafael Mendonça França2012-10-291-0/+6
|
* Merge pull request #7587 from elia/fix-too-eager-loadingRafael Mendonça França2012-10-293-6/+17
| | | | | | Should not eager_load app/assets Conflicts: railties/CHANGELOG.md
* USe the released version of sprockets-rails in a new Rails 4 applicationRafael Mendonça França2012-10-271-1/+1
|
* Job consumer logs to Rails.logger by defaultJeremy Kemper2012-10-262-0/+2
|
* changed test case nameTima Maslyuchenko2012-10-231-1/+1
|
* Remove extra line in Gemfile under turbolinks.Geoffrey Roguelon2012-10-211-1/+1
|
* Merge branch 'master' of github.com:lifo/docrailsVijay Dev2012-10-211-1/+1
|\ | | | | | | | | | | Conflicts: activesupport/lib/active_support/core_ext/hash/slice.rb guides/source/active_support_core_extensions.md
| * Corrected the logic in production.rb comment.Robb Shecter2012-10-181-1/+1
| |
| * Moving code base to 1.9 hash syntaxAvnerCohen2012-10-163-7/+7
| |
| * Hash syntax to 1.9 styleAvnerCohen2012-10-152-3/+3
| |
* | We don't need this anymore since we had a sprockets-rails releaseRafael Mendonça França2012-10-191-3/+0
| |
* | Remove warning setting eager_loadRafael Mendonça França2012-10-181-0/+1
| |
* | Don't use action_controller.perform_caching to enable rack-rack.Rafael Mendonça França2012-10-183-7/+14
| | | | | | | | | | Setting the action_dispatch.rack_cache options to true or a hash should be the way to enable it.
* | Fix the app_generator and plugin_new testsRafael Mendonça França2012-10-182-1/+4
| |
* | Now the Sprockets railtie lives in sprockets/railtieRafael Mendonça França2012-10-183-3/+3
| |
* | Change back to official sprockets-railsJoshua Peek2012-10-171-2/+2
| |
* | Merge pull request #7968 from josh/only-precompile-app-assets-by-defaultRafael Mendonça França2012-10-171-1/+1
|\ \ | | | | | | Only compile non-js/css under app/assets by default
| * | Only compile non-js/css under app/assets by defaultJoshua Peek2012-10-161-1/+1
| | |
* | | Switch to new sprockets-rails pluginJoshua Peek2012-10-155-134/+59
|/ /
* | Use sprockets-rails masterJoshua Peek2012-10-151-2/+2
| |
* | Use sprockets-rails branch for nowJoshua Peek2012-10-151-2/+2
| |
* | Merge branch 'master' into asset-path-helperJoshua Peek2012-10-15100-507/+513
|\ \ | | | | | | | | | | | | Conflicts: railties/test/application/configuration_test.rb
| * | Fix typo in #7941Jeremy Kemper2012-10-141-1/+1
| | |
| * | Use Ruby 1.9 Hash syntax in railtiesRobin Dupret2012-10-1494-447/+447
| | |
| * | Test that a Rails.queue consumer is automatically started in productionJeremy Kemper2012-10-133-3/+14
| | |
| * | Backpedal from class-oriented config.queue. Set an actual queue instance.Jeremy Kemper2012-10-127-18/+10
| | |
| * | Tighten up asset precompile testsJeremy Kemper2012-10-122-4/+3
| | |
| * | Remove the queue container. Premature consolidation. Set up and maintain ↵Jeremy Kemper2012-10-123-14/+9
| | | | | | | | | | | | queues in the classes that use them instead.
| * | Merge pull request #7891 from schneems/schneems/rake_command_warningJosé Valim2012-10-121-23/+32
| |\ \ | | | | | | | | Prompt to run rake when accidentally typed rails
| | * | Prompt to run rake when accidentally typed railsschneems2012-10-121-23/+32
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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) =================================================== ```
* | | | Remove old asset_path from rails configJoshua Peek2012-10-152-25/+1
|/ / /
* | | ActiveSupport::SynchronousQueue doesn't have the drain method.Rafael Mendonça França2012-10-121-4/+4
| | | | | | | | | | | | | | | Now we are using teh SynchronousQueue in the test environment instead of the TestQueue
* | | Move the TestQueue tests to the proper fileRafael Mendonça França2012-10-121-47/+0
| | |
* | | Add .rake to `rake notes` and `rake notes:custom`Brent J. Nordquist2012-10-123-8/+12
| | |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-17 23:01:42 +0000