aboutsummaryrefslogtreecommitdiffstats
path: root/railties/CHANGELOG.md
Commit message (Collapse)AuthorAgeFilesLines
* Deprecate `Rails::Generators::ActiveModel#update_attributes`Carlos Antonio da Silva2013-01-121-0/+15
| | | | | | | | | | | | | | | | Deprecate #update_attributes in favor of `#update`. ORMs that implement `Generators::ActiveModel#update_attributes` should change to `#update`. Scaffold controller generators should change calls like: @orm_instance.update_attributes(...) to: @orm_instance.update(...) This goes along with the addition of `ActiveRecord::Base#update`, introduced in cb2bd4aa619d9329c42aaf6d9f8eacc616ce53f4.
* Add changelog entry for scaffold generator and jbuilder changesCarlos Antonio da Silva2013-01-111-0/+9
| | | | | | | Introduced in 3bfd99defb559af0b017ee920ca714aa1e367fdd. Related to #8840. [ci skip]
* new README generated for new appsXavier Noria2013-01-081-0/+5
|
* doc/README_FOR_APP is no longer generatedXavier Noria2013-01-081-0/+6
|
* Take the heat :fire:Jeremy Kemper2013-01-061-0/+2
|
* Introduce ./bin for your app's executables: bin/bundle, bin/rails, bin/rake. ↵Jeremy Kemper2013-01-061-0/+14
| | | | Executable scripts are versioned code like the rest of your app. To generate a stub for a bundled gem: 'bundle binstubs unicorn' and 'git add bin/unicorn'
* Remove the content_tag_for change from CHANGELOG since it was revertedRafael Mendonça França2013-01-051-5/+3
|
* config.assets.enabled is now true by defaultDavid Heinemeier Hansson2013-01-051-0/+6
|
* Move changelog entry in railties to the topCarlos Antonio da Silva2013-01-041-8/+7
| | | | Other minor changelog improvements [ci skip]
* Small typo fix in railties/CHANGELOG.mdMatt Bridges2013-01-041-1/+1
|
* This commit fixes issue #8628Mykola Kyryk2013-01-041-0/+7
| | | | | | | | | | | | Allow environment name to start with a substring of the default environment names. For example: tes, pro, prod, dev, devel, etc. Fixing identation. Adding test for Rails::Console.parse_arguments method. Fix issue 8628 for Rails::DBConsole.
* Add missing changelog entry for #8676 [ci skip]Jiri Pospisil2013-01-021-0/+4
|
* quote column names in generated fixture filesYves Senn2012-12-261-0/+6
|
* Explicit options should have precedence over railsrc on the `rails new`Rafael Mendonça França2012-12-241-0/+4
| | | | | | command Closes #8545
* Move background jobs to the 'jobs' branch until fully baked. Not shipping ↵Jeremy Kemper2012-12-211-4/+0
| | | | with Rails 4.0.
* Revert "Make sure that RAILS_ENV is set when accessing Rails.env"Andy Lindeman2012-12-211-2/+0
| | | | | | | | This reverts commit b3125c89f42968bec6ee0b92ab93e36dbc36d5c3. * It is not desirable to set `ENV['RAILS_ENV']`; otherwise, it will leak through to rake tasks such as `rake test` or `rake spec`. See #7175 for more details.
* Update Migration and 4.0 Release Guides, Changelogs [#8267]Marc-Andre Lafortune2012-12-211-0/+4
|
* fix railties CHANGELOG [ci skip]Francesco Rodriguez2012-12-181-2/+3
|
* Revert "Merge pull request #7587 from elia/fix-too-eager-loading"Rafael Mendonça França2012-12-181-2/+0
| | | | | | | | | | This reverts commit 3663057518eb9acf9b1e72f47dcb07038e6b7368. REASON: This caused a regression that add app folder in the eager load path. See #8146 for more information. Conflicts: railties/CHANGELOG.md
* Fix changelogDavid Heinemeier Hansson2012-12-181-3/+1
|
* MergeDavid Heinemeier Hansson2012-12-181-0/+6
|\
| * HTML formatting to Rails::InfoController#routesschneems2012-12-171-0/+4
| | | | | | | | | | | | | | | | | | | | This PR adds formatting and meta-data to the display of the internal routes. Users can now toggle between showing helpers with the `_path` or _`url` suffix. There are multiple ways to achieve this, this method uses partials for formatting and meta-data. The partials can be re-used when rendering `routing_error.erb`, though that will need to be in a separate PR. ![](http://f.cl.ly/items/3A2p3c1T1t2f2X2R2K2S/Screen%20Shot%202012-12-12%20at%202.28.01%20PM.png) ATP Railties
* | Add app/models/concerns and app/controllers/concerns to the default ↵David Heinemeier Hansson2012-12-181-0/+4
|/ | | | directory structure and load path
* Convert changelogs to 1.9 hash style and fix some formatting [ci skip]Carlos Antonio da Silva2012-12-141-7/+8
|
* Use Rails to Render Default Index Pageschneems2012-12-101-1/+5
| | | | | | | | | | | | | | | This is an alternative implementation to #7771 thanks to the advice of @spastorino Rails is a dynamic framework that serves a static index.html by default. One of my first questions ever on IRC was solved by simply deleting my public/index.html file. This file is a source of confusion when starting as it over-rides any set "root" in the routes yet it itself is not listed in the routes. By making the page dynamic by default we can eliminate this confusion. This PR moves the static index page to an internal controller/route/view similar to `rails/info`. When someone starts a rails server, if no root is defined, this route will take over and the "dynamic" index page from rails/welcome_controller will be rendered. These routes are only added in development. If a developer defines a root in their routes, it automatically takes precedence over this route and will be rendered, with no deleting of files required. In addition to removing this source of confusion for new devs, we can now use Rails view helpers to build and render this page. While not the primary intent, the added value of "dogfooding" should not be under-estimated. The prior PR #7771 had push-back since it introduced developer facing files. This PR solves all of the same problems, but does not have any new developer facing files (it actually removes one). cc/ @wsouto, @dickeyxxx, @tyre, @ryanb, @josevalim, @maxim, @subdigital, @steveklabnik ATP Railties and Actionpack.
* Add ENV['RACK_ENV'] support to rake runner/console/server.kennyj2012-12-061-0/+4
|
* Add db to the list of default annotation foldersAntonio Cangiano2012-12-011-0/+2
|
* require bundler groups to include rake-tasks in enginesYves Senn2012-11-181-0/+5
| | | | | | | | If you generate a full engine, this will include rake tasks from your gem under the `app` namespace. For example if you have a dependency on `rspec-rails` in your engine's `gemspec`. You will get the task `app:spec` Closes #8229
* cleanup, remove whitspace from railties CHANGELOGYves Senn2012-11-181-2/+2
|
* Adding sqlserver.yml template to satisfy "-d sqlserver" being givenRobert Nesius2012-11-161-0/+5
| | | | invocations of "rails new".
* Add ChangeLog entry.Nicolas Despres2012-11-131-0/+2
|
* `plugin new` adds dummy app tasks when necessary.Yves Senn2012-11-081-1/+6
| | | | | | | Closes #8121 The `plugin new` generator always adds the dummy app rake tasks, when a dummy app was created.
* Make sure that RAILS_ENV is set when accessing Rails.envSteve Klabnik2012-10-311-0/+2
| | | | Fixes #8025
* Merge pull request #7587 from elia/fix-too-eager-loadingRafael Mendonça França2012-10-291-0/+2
| | | | | | Should not eager_load app/assets Conflicts: railties/CHANGELOG.md
* Backpedal from class-oriented config.queue. Set an actual queue instance.Jeremy Kemper2012-10-121-2/+2
|
* Add .rake to `rake notes` and `rake notes:custom`Brent J. Nordquist2012-10-121-0/+2
|
* Update test locationsMike Moore2012-10-091-0/+3
| | | | | | | | | | | | | | Change the default test locations to avoid confusion around the common testing terms "unit" and "functional". Add new rake tasks for the new locations, while maintaining backwards compatibility with the old rake tasks. New testing locations are as follows: app/models -> test/models (was test/units) app/helpers -> test/helpers (was test/units/helpers) app/controllers -> test/controllers (was test/functional) app/mailers -> test/mailers (was test/functional)
* Add missing entry in CHANGELOG about config.assets.cache changeGuillermo Iguaran2012-10-091-2/+7
|
* Make Rails.public_path return a PathnamePrem Sichanugrist2012-10-021-0/+2
|
* Remove highly uncommon `config.assets.manifest` option for moving the ↵Guillermo Iguaran2012-09-191-0/+5
| | | | | | manifest path. This option is now unsupported in sprockets-rails.
* Update changelogs to add entries about strong_parameters integrationGuillermo Iguaran2012-09-191-0/+11
|
* change app/plugin generators to be more SCM agnosticDerek Prior2012-09-121-0/+10
| | | | | | | | | | | | | | | | | Users of other SCM's can now generate rails apps that will add the "empty" directories to source control, but will not have a useless .gitignore or mis-named .gitkeep files. * Change `rails new` and `rails plugin new` generators to name the `.gitkeep` as `.keep` in a more SCM-agnostic way. * Change `--skip-git` option to only skip the `.gitignore` file and still generate the `.keep` files. * Add `--skip-keeps` option to skip the `.keep` files. It closes #2800.
* fixed support for DATABASE_URL for rake db tasksGrace Liu2012-09-111-0/+2
| | | | | | | | | | | | - added tests to confirm establish_connection uses DATABASE_URL and Rails.env correctly even when no arguments are passed in. - updated rake db tasks to support DATABASE_URL, and added tests to confirm correct behavior for these rake tasks. (Removed establish_connection call from some tasks since in those cases the :environment task already made sure the function would be called) - updated Resolver so that when it resolves the database url, it removes hash values with empty strings from the config spec (e.g. to support connection to postgresql when no username is specified).
* Support MySQL SSL in rails dbconsole.needfeed2012-09-101-0/+3
|
* CHANGELOGs are now per branchXavier Noria2012-08-281-2479/+1
| | | | | | | | | | Changes in old branches needed to be manually synched in CHANGELOGs of newer ones. This has proven to be brittle, sometimes one just forgets this manual step. With this commit we switch to CHANGELOGs per branch. When a new major version is cut from master, the CHANGELOGs in master start being blank. A link to the CHANGELOG of the previous branch allows anyone interested to follow the history.
* Deprecate config.threadsafe!José Valim2012-08-211-0/+2
|
* Fix handling SCRIPT_NAME from within mounted engine'sPiotr Sarnacki2012-08-111-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When you mount your application at a path, for example /myapp, server should set SCRIPT_NAME to /myapp. With such information, rails application knows that it's mounted at /myapp path and it should generate routes relative to that path. Before this patch, rails handled SCRIPT_NAME correctly only for regular apps, but it failed to do it for mounted engines. The solution was to hardcode default_url_options[:script_name], which is not the best answer - it will work only when application is mounted at a fixed path. This patch fixes the situation by respecting original value of SCRIPT_NAME when generating application's routes from engine and the other way round - when you generate engine's routes from application. This is done by using one of 2 pieces of information in env - current SCRIPT_NAME or SCRIPT_NAME for a corresponding router. This is because we have 2 cases to handle: - generating engine's route from application: in this situation SCRIPT_NAME is basically SCRIPT_NAME set by the server and it indicates the place where application is mounted, so we can just pass it as :original_script_name in url_options. :original_script_name is used because if we use :script_name, router will ignore generating prefix for engine - generating application's route from engine: in this situation we already lost information about the SCRIPT_NAME that server used. For example if application is mounted at /myapp and engine is mounted at /blog, at this point SCRIPT_NAME is equal /myapp/blog. Because of that we need to keep reference to /myapp SCRIPT_NAME by binding it to the current router. Later on we can extract it and use when generating url Please note that starting from now you *should not* use default_url_options[:script_name] explicitly if your server already passes correct SCRIPT_NAME to rack env. (closes #6933)
* Revert "The application generator generates `public/humans.txt` with some ↵David Heinemeier Hansson2012-08-071-2/+0
| | | | basic data". I dont consider this something most people is going to want most of the time. If you want to add it in your own app, knock yourself out. But it doesnt belong in Rails imo
* Add references statements to migration generatorAleksey Magusev2012-07-081-0/+11
| | | | | | | | | | | | | AddXXXToYYY/RemoveXXXFromYYY migrations are produced with references statements, for instance rails g migration AddReferencesToProducts user:references supplier:references{polymorphic} will generate the migration with: add_reference :products, :user, index: true add_reference :products, :supplier, polymorphic: true, index: true
* Add changelog entry for polymorphic option in model generatorCarlos Antonio da Silva2012-06-271-0/+10
| | | | | Pull request #6856, merged in 52f6e47682003c83b0466bf5e140ee302498a226. [ci skip]
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-01 08:11:09 +0000