aboutsummaryrefslogtreecommitdiffstats
path: root/railties/lib/rails/generators
Commit message (Collapse)AuthorAgeFilesLines
* Remove buggy and unnecessary logicSam Ruby2013-03-271-7/+0
| | | | based on a discussion with @rafaelfranca
* Cosmetic cleanup of generated GemfileSam Ruby2013-03-271-17/+14
| | | | | | - Remove obsolete/misleading comment about assets only being used production - Remove unnecessary group :assets - Eliminate blank lines if options[:skip_javascript] is not specified
* Put coffee-rails in top-level of generated GemfileGabe Kopley2013-03-241-15/+27
| | | | v3 of pull request based on additional feedback from @jeremy
* Use jquery-rails from githubSam Ruby2013-03-241-1/+3
| | | | completes https://github.com/rails/rails/commit/6f3f0f86332004fcee5c2f05d52bbff08c22f980
* Merge pull request #8501 from charliesome/version-to-sRafael Mendonça França2013-03-233-4/+4
|\ | | | | Add #to_s method to VERSION modules
| * remove references to *::VERSION, replace with *.versionCharlie Somerville2013-03-213-4/+4
| |
* | Better styles for the CSS [ci skip]Rafael Mendonça França2013-03-233-38/+38
|/
* Don't generate a scaffold.css if no-assetsKevin Glowacz2013-03-201-0/+1
|
* fix sentence [ci skip]Neeraj Singh2013-03-191-1/+1
|
* config.ru uses the effective Rack appYves Senn2013-03-151-1/+1
| | | | | | | | | | We used to pass the Rails::Application subclass to #run. The Rails server then called #to_app to convert that class to the actual Rack application. if you surround `#run` with a call to `#map` the server no longer convertes the class to the instance and we end up with unnecessary delegation calls on every request.
* 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
* 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-111-3/+4
|\ | | | | Add `rails test` command to run the test suite
| * Make sure that `rails test` load test in test envPrem Sichanugrist2013-03-091-1/+1
| |
| * Improve wording for rails test commandDalibor Nasevic2013-03-091-2/+2
| |
| * Load fixtures only when running suites, or `-f`Prem Sichanugrist2013-03-091-2/+3
| | | | | | | | | | | | * `rails test -f` will run the test suites with all fixtures loaded * New application will now generated without `fixtures :all` line enabled by default.
* | Make sure that debugger isn't included in production environment.Teng Siong Ong2013-03-091-1/+1
|/
* Remove extra whitespace and fix a commentAgis Anastasopoulos2013-03-091-2/+2
| | | minor comment fix for consistency
* add prompt to 422 page to check logsNihad Abbasov2013-03-041-2/+3
|
* 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)
* | :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
|
* 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
|/
* 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
* 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.
* move config.assets.precompile into config/application.rbYves Senn2013-02-202-6/+4
|
* 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.
* 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.
* Added notice message for destroy method in scaffoldRahul P. Chaudhari2013-02-101-1/+1
|
* Fix article for generator nameRyunosuke SATO2013-02-071-2/+2
| | | | Use 'some' instead of 'a/an'.
* Add --rc description on the command linerobertomiranda2013-02-041-0/+3
|
* Add --no-rc description on the command linerobertomiranda2013-02-021-0/+3
|
* Remove BestStandardsSupport middlewareGuillermo Iguaran2013-01-291-3/+0
|
* Merge pull request #8303 from jeremywrowe/masterRafael Mendonça França2013-01-251-1/+1
|\ | | | | | | | | | | | | 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-161-1/+1
| | | | | | | | | | | | application. EG: `rails new something.awesome.com` Conflicts: railties/CHANGELOG.md
* | 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.