aboutsummaryrefslogtreecommitdiffstats
path: root/railties
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | remove AR auto-explain (config.auto_explain_threshold_in_seconds)Yves Senn2013-02-243-19/+0
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | We discussed that the auto explain feature is rarely used. This PR removes only the automatic explain. You can still display the explain output for any given relation using `ActiveRecord::Relation#explain`. As a side-effect this should also fix the connection problem during asset compilation (#9385). The auto explain initializer in the `ActiveRecord::Railtie` forced a connection.
* / / Use sprockets-rails 2.0.0.rc3 in new appsGuillermo Iguaran2013-02-241-1/+1
|/ /
* | Revert "move config.assets.precompile into config/application.rb"Yves Senn2013-02-243-10/+6
| | | | | | | | | | | | | | This reverts commit 304f4d4c25ccabdbf97d37dd7a92a54d0b63a9c9. As it turns out everything should behave as it did and we don't need to move this configuration option.
* | guides/rails_guides moved up and out of the railties directorySam Ruby2013-02-231-1/+1
| |
* | Fix backwards compatibility with Rails 3 apps.Steve Klabnik2013-02-223-40/+52
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When we removed script/rails and introduced bin/rails, we accidentally introduced a regression. If you install Rails 4 as a gem, then try to do something in a Rails 3 application: $ rails g This will throw the 'please type rails new foo' message rather than the proper generator documentation message. This is because older apps don't have bin/rails. Therefore, we now *prefer* bin/rails, but still search for script/rails, and exec the one we find.
* | Update railties/lib/rails/application/configuration.rbiwiznia2013-02-211-3/+3
| | | | | | Better comment for database_configuration method
* | Update railties/lib/rails/application/configuration.rbiwiznia2013-02-211-1/+1
| | | | | | Changed comment that referenced the property #database_configuration_file, now it's paths["config/database"]
* | remove uncommented railties boot_test.rbYves Senn2013-02-211-20/+0
| |
* | Merge pull request #9341 from senny/move_precompiled_asset_config_to_applicationRafael Mendonça França2013-02-203-6/+10
|\ \ | | | | | | move config.assets.precompile into config/application.rb
| * | move config.assets.precompile into config/application.rbYves Senn2013-02-203-6/+10
| | |
* | | update changelogTerence Lee2013-02-211-0/+3
| | |
* | | run the load_structure test in the test environmentTerence Lee2013-02-211-3/+10
| | |
* | | test DATABASE_URL without database.yml aroundTerence Lee2013-02-211-0/+2
| | |
* | | standardize database_configuration to a hashTerence Lee2013-02-211-2/+6
|/ / | | | | | | | | | | | | make connection_url_to_hash a class method This als prevents loading database.yml if it doesn't exist but DATABASE_URL does
* | Better not use tab chars in the generator templateAkira Matsuda2013-02-201-5/+5
| |
* | Fix rake routes output in railties testCarlos Antonio da Silva2013-02-191-2/+4
| |
* | Remove config.autoload_paths from config/application.rbAndrew White2013-02-191-3/+0
| | | | | | | | | | | | | | | | | | | | Most application developers shouldn't be adding paths to `config.autoload_paths` as it won't be eagerly loaded so remove it from the generated config/application.rb file. If a developer does want to autoload from paths outside of the app directory then they should add the path to `config.eager_load_paths` as these paths are also autoloaded as well.
* | Don't unhook autoloading in productionAndrew White2013-02-191-7/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Whilst autoloading is known to be not threadsafe, leaving it in place is a softer solution than failing hard when an application is deployed. Many older applications will have paths added to `autoload_paths` and ideally these should be eagerly loaded to be threadsafe. However one of these paths is quite often lib which could lead to unintended consequences due to the 'junk drawer' nature of this directory. Developers should refrain from adding paths to `autoload_paths` or `eager_load_paths` and use custom folders inside app for code that needs to be eagerly loaded and use `require` or `require_dependency` to explicitly load code from other locations.
* | Revert "Deprecate the `eager_load_paths` configuration"Andrew White2013-02-197-91/+66
| | | | | | | | | | | | | | | | | | | | | | Because of the possibility of lib being unintentionally eager loaded it's been agreed that we'll leave autoload paths and eager load paths separate for Rails 4.0. This reverts commit 0757b3388ffe4f44b60de950d40e18ef05055931. Conflicts: railties/CHANGELOG.md
* | editorial tweaksXavier Noria2013-02-191-1/+1
| |
* | Use strip_heredoc in the tests as well.Steve Klabnik2013-02-181-5/+6
| | | | | | | | Thanks @sikachu. :sweat_smile:
* | Add message when you have no routes defined.Steve Klabnik2013-02-181-0/+15
| | | | | | | | | | | | Print a message in both `rake routes` and at GET "/rails/info/routes" that lets you know you have no routes defined, as well as linking to the Rails Guide on the topic.
* | Gist URLs are now namespacedAkira Matsuda2013-02-181-3/+3
| | | | | | | | see: https://github.com/blog/1406-namespaced-gists
* | Added extra comment when a migration already exists of the same name.wangjohn2013-02-151-1/+1
| | | | | | | | | | | | User should know that he can overwrite the previous migration. This comes in handy especially when generating models which were previously created then removed.
* | Add changelog entry for #9177 [ci skip]Carlos Antonio da Silva2013-02-111-4/+11
| | | | | | | | Add test:all and test:all:db rake tests to speed up full test runs.
* | Prefer Ruby 2.0; require 1.9.3+Jeremy Kemper2013-02-091-2/+2
| |
* | Added notice message for destroy method in scaffoldRahul P. Chaudhari2013-02-103-1/+6
| |
* | Fix article for generator nameRyunosuke SATO2013-02-071-2/+2
| | | | | | | | Use 'some' instead of 'a/an'.
* | Added test:all and test:all:db tasks to speed up full test runs.Ryan Davis2013-02-041-0/+12
| | | | | | | | | | | | | | | | | | | | Speed up depends on the number of test phases (N) you have for your app, but it is roughly a 1/N improvement. In my app, it goes from 15.51s to 5.56s. Inspired by http://ngauthier.com/2012/02/quick-tests-with-bash.html Reviewed by @tenderlove
* | Merge pull request #9175 from robertomiranda/add--rc-descGuillermo Iguaran2013-02-041-0/+3
|\ \ | | | | | | Add --rc description on the command line
| * | Add --rc description on the command linerobertomiranda2013-02-041-0/+3
| | |
* | | Use --rc= instead of --rcrobertomiranda2013-02-041-2/+6
|/ /
* | Add --no-rc description on the command linerobertomiranda2013-02-021-0/+3
| |
* | Refactor --rc optionGuillermo Iguaran2013-02-021-6/+1
| |
* | Add --rc option to support the load of a custom rc fileAmparo Luna2013-02-012-1/+11
| |
* | Prefer File.read over File.open.readAkira Matsuda2013-02-011-1/+1
| |
* | --no-rc in the railties testsAkira Matsuda2013-02-012-2/+2
| | | | | | | | so that the tester's local .railsrc file does not affect the test results
* | Add --no-rc option to skip the loading of railsrc fileAmparo Luna2013-01-312-6/+12
| |
* | Remove BestStandardsSupport middlewareGuillermo Iguaran2013-01-295-41/+3
| |
* | Merge pull request #8303 from jeremywrowe/masterRafael Mendonça França2013-01-253-1/+11
|\ \ | | | | | | | | | | | | | | | | | | Fixes improper database name when creating a new rails app with a '.' Conflicts: railties/CHANGELOG.md
| * | Fixes improper database name when a '.' is included while creating a new railsJeremy W. Rowe2013-01-163-1/+11
| | | | | | | | | | | | | | | | | | application. EG: `rails new something.awesome.com` Conflicts: railties/CHANGELOG.md
* | | Deprecate the `eager_load_paths` configurationAndrew White2013-01-247-66/+91
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since the default in Rails 4.0 is to run in 'threadsafe' mode we need to eager load all of the paths in `autoload_paths` so we alias `eager_load_paths` to it. This may have unintended consequences if you have added 'lib' to `autoload_paths` such as loading unneeded code or code intended only for development and/or test environments. If this applies to your application you should thoroughly check what is being eager loaded.
* | | Depend on thor >= 0.17.0Carlos Antonio da Silva2013-01-231-1/+1
| | |
* | | Revert "Merge pull request #7873 from steveklabnik/update_initializer"Carlos Antonio da Silva2013-01-222-9/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 43e14f8ff203c21646f733d35bdde4e68da70a3b, reversing changes made to bb17a0f085aba40a1952612f6c98b2a5804a1152. Conflicts: railties/lib/rails/generators/rails/app/templates/config/application.rb railties/lib/rails/generators/rails/app/templates/config/initializers/locale.rb Reason: setting the Time.zone in an after_initialize block can become a problem for people upgrading, since it's not going to be available when config/initializers run, and people might be relying on it. An example that I noticed was with the Chronic gem, for date/time parsing. It requires us to configure the time class to be Time.zone, and doing that in an initializer no longer worked with these changes, so reverting is the safer path for now.
* | | Revert "Set the default timezone after the initialization since the ↵Carlos Antonio da Silva2013-01-221-11/+1
| | | | | | | | | | | | | | | | | | configuration" This reverts commit 39374aa925a7d670b039c0c0c9aa9f4aef19466b.
* | | Remove unnecessary requireRyunosuke SATO2013-01-221-1/+0
| | | | | | | | | | | | `require 'rubygems'` is already required in Ruby 1.9 or later.
* | | Merge pull request #8557 from timraymond/add_back_engines_and_deprecateRafael Mendonça França2013-01-225-5/+46
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | Adding Back Rails::Engine::Railties#engines Conflicts: railties/CHANGELOG.md
| * | | Adding Back Rails::Engine::Railties#enginesTim Raymond2013-01-035-5/+46
| | | | | | | | | | | | | | | | | | | | Removing it breaks functionality with gems such as Thinking Sphinx. This restores it with a deprecation warning. Closes #8551
* | | | Fix asset_path in mounted enginePiotr Sarnacki2013-01-211-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Historically serving assets from a mountable engine could be achieved by running ActionDispatch::Static as a part of engine middleware stack or to copy assets prefixed with an engine name. After introduction of assets pipeline this is not needed as all of the assets are served or compiled into main application's assets. This commit removes the obsolete line making asset_path always generate paths relative to the root or config.relative_url_root if it's set. (closes #8119)
* | | | Restore and adapt the implementation reverted atRafael Mendonça França2013-01-191-0/+48
| | | | | | | | | | | | | | | | | | | | | | | | https://github.com/rails/rails/commit/cc1c3c5be061e7572018f734e5239750ab449e3f Now instead of raise, we log by default in development and test
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-16 11:01:15 +0000