aboutsummaryrefslogtreecommitdiffstats
path: root/railties/lib
Commit message (Collapse)AuthorAgeFilesLines
* make new rails apps log to STDOUTTerence Lee2013-03-152-5/+3
|
* Add support for generate scaffold password:digestSam Ruby2013-03-137-13/+29
| | | | | | | | | | * adds password_digest attribute to the migration * adds has_secure_password to the model * adds password and password_confirmation password_fields to _form.html * omits password entirely from index.html and show.html * adds password and password_confirmation to the controller * adds unencrypted password and password_confirmation to the controller test * adds encrypted password_digest to the fixture
* Stop calling "super" twice in Rails::Server#appCarlos Antonio da Silva2013-03-121-1/+4
| | | | Cache the value of "super" in a variable and use it instead.
* Mention that debugging can be slow.Steve Klabnik2013-03-111-0/+2
| | | | | | https://github.com/rails/rails/pull/3180\#issuecomment-14705821 has mention of rendering going from 1-2ms to 4 seconds with this on, which seems reasonable: debugging is slow.
* Merge pull request #9080 from sikachu/master-rails-testRafael Mendonça França2013-03-114-55/+189
|\ | | | | Add `rails test` command to run the test suite
| * Make sure that `rails test` load test in test envPrem Sichanugrist2013-03-093-6/+11
| |
| * Update Rake tasks to call `rails test` insteadPrem Sichanugrist2013-03-091-52/+28
| | | | | | | | | | Also, print out deprecation warning for other rake tasks except `rake test` and `rake` (default)
| * Improve wording for rails test commandDalibor Nasevic2013-03-092-19/+19
| |
| * Load fixtures only when running suites, or `-f`Prem Sichanugrist2013-03-092-3/+21
| | | | | | | | | | | | * `rails test -f` will run the test suites with all fixtures loaded * New application will now generated without `fixtures :all` line enabled by default.
| * Add support for MiniTest flags in TestRunnerPrem Sichanugrist2013-03-092-39/+67
| | | | | | | | | | Any flags that got set will be passed through to MiniTest::Unit.runner, such as `-n`, `-s-, and `-v`.
| * Add `rails test` command to run the test suitePrem Sichanugrist and Chris Toomey2013-03-092-0/+107
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | To run the whole test suite: $ rails test To run the test file(s): $ rails test test/unit/foo_test.rb [test/unit/bar_test.rb ...] To run the test suite $ rails test [models,helpers,units,controllers,mailers,...] For more information, see `rails test --help`. This command will eventually replacing `rake test:*`, and `rake test` command will actually invoking `rails test` instead.
* | Make sure that debugger isn't included in production environment.Teng Siong Ong2013-03-091-1/+1
|/
* Renumbering the comments in the application boot process.wangjohn2013-03-091-4/+4
|
* Remove extra whitespace and fix a commentAgis Anastasopoulos2013-03-091-2/+2
| | | minor comment fix for consistency
* Fix rails console --sandboxJon Leighton2013-03-081-1/+3
| | | | | | I've also added a proper acceptance test which reproduced the issue. Closes #9513, #9515.
* add prompt to 422 page to check logsNihad Abbasov2013-03-041-2/+3
|
* Bring config.allow_concurrency backJosé Valim2013-03-032-19/+42
| | | | | Since the Rack::Lock still exists in development, let's provide a way to disable it explicitly.
* Merge pull request #9512 from Jacke/masterGuillermo Iguaran2013-03-023-33/+126
|\ | | | | New 404, 422, 500 pages, they are more stylish and bring ruby essence…
| * New beauty pages(404, 422, 500)Stanislav2013-03-023-33/+126
| | | | | | | | | | | | moving changelog note to unreleased section New beauty pages(404, 422, 500)
* | Remove hard coded references to Active Record in railtiesJosé Valim2013-03-021-6/+7
| |
* | :scissors: extra blank lineAkira Matsuda2013-03-021-1/+0
|/
* Ensure plugins generated with plugin new can boot the dummy applicationJosé Valim2013-02-285-14/+35
|
* There's no need to access Railties through self.classSantiago Pastorino2013-02-271-1/+2
| | | | Closes #9386
* Use less hyperbole in the language re: allowed parametersDavid Czarnecki2013-02-261-1/+1
|
* Merge pull request #9419 from banyan/change-default-root-route-helperGuillermo Iguaran2013-02-252-2/+2
|\ | | | | Change default root route helper
| * Change default root route helperKohei Hasegawa2013-02-262-2/+2
| |
* | Apparently we can't get away from adding lib to the load pathJosé Valim2013-02-251-0/+1
| |
* | Plugins can use a similar bootscript to Rails appsJosé Valim2013-02-251-8/+3
| |
* | Bump sass-rails and coffee-rails to 4.0.0.beta1 in GemfileGuillermo Iguaran2013-02-251-2/+2
| |
* | Remove sprockets-rails from the Gemfile generatorrobertomiranda2013-02-251-1/+0
|/
* Preparing for 4.0.0.beta1 releaseDavid Heinemeier Hansson2013-02-251-1/+1
|
* Revert "Use sass compressor as the default CSS compressor"Guillermo Iguaran2013-02-251-1/+1
| | | | | | | This reverts commit 3eef1c7c5d0c4538efb9e061b6fe68011f0352b1. The css compressor should be set in sass-rails plugin. Check https://github.com/rails/sass-rails/commit/339529f9f6433047df6358c0439e6641cb74f045 for the fix.
* Use sass compressor as the default CSS compressorRafael Mendonça França2013-02-251-1/+1
| | | | | | | With the new sprockets-rails we need to explicitly set the CSS compressor. See https://github.com/rails/sprockets-rails#changes-from-rails-3x
* Improve `rake stats` for JavaScript and CoffeeScript.Hendy Tanata2013-02-252-46/+101
| | | | Ignore block comments and calculates number of functions.
* Merge pull request #9401 from sikachu/master-remove-builder-optionRafael Mendonça França2013-02-241-14/+0
|\ | | | | Remove `--builder` option from `rails` command
| * Remove `--builder` option from `rails` commandPrem Sichanugrist2013-02-241-14/+0
| | | | | | | | | | | | | | Ability to use a custom builder by passing `--builder` (or `-b`) has been removed. Consider using application template instead. See this guide for more detail: http://guides.rubyonrails.org/rails_application_templates.html
* | Merge pull request #9400 from senny/remove_auto_explain_threshold_in_secondsXavier Noria2013-02-242-10/+0
|\ \ | | | | | | remove config.auto_explain_threshold_in_seconds
| * | remove AR auto-explain (config.auto_explain_threshold_in_seconds)Yves Senn2013-02-242-10/+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-242-4/+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-222-11/+16
| | | | | | | | | | | | | | | 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"]
* Merge pull request #9341 from senny/move_precompiled_asset_config_to_applicationRafael Mendonça França2013-02-202-6/+4
|\ | | | | move config.assets.precompile into config/application.rb
| * move config.assets.precompile into config/application.rbYves Senn2013-02-202-6/+4
| |
* | 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
|
* 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.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-20 14:50:54 +0000