aboutsummaryrefslogtreecommitdiffstats
path: root/railties/CHANGELOG.md
Commit message (Collapse)AuthorAgeFilesLines
* actually autoload all second-level directories called `app/*/concerns`Alex Robbin2014-12-261-0/+4
|
* Start Rails 5 development :tada:Rafael Mendonça França2014-11-281-208/+1
| | | | | | | We will support only Ruby >= 2.1. But right now we don't accept pull requests with syntax changes to drop support to Ruby 1.9.
* Generators add foreign keys on referencesDerek Prior2014-11-251-0/+5
| | | | | | | | | | | If you run a generator such as: ``` rails generate model accounts supplier:references ``` The resulting migration will now add the corresponding foreign key constraint unless the reference was specified to be polymorphic.
* Add a CHANGELOG entry for #16622 and a6de6f5 [ci skip]Zachary Scott2014-11-241-0/+4
|
* Merge pull request #17700 from ShunsukeAida/ignore_log_as_a_wholeYves Senn2014-11-211-0/+5
| | | | | | why not gitignore /log as a whole? [ci skip]
* Improve railties changelog entry and move latest to the top [ci skip]Carlos Antonio da Silva2014-11-121-8/+7
|
* Merge pull request #17593 from igas/paths-unshift-arityRafael Mendonça França2014-11-121-0/+5
|\ | | | | Fix Rails::Paths::Path.unshift interface
| * Fix Rails::Paths::Path.unshift interfaceIgor Kapkov2014-11-121-0/+5
| |
* | Merge pull request #17348 from DavidGeukers/rake_test_allDavid Heinemeier Hansson2014-11-121-0/+6
|\ \ | |/ |/| simplify rake test vs rake test:all
| * Simplify rake test vs rake test:allDavid Geukers2014-11-101-0/+6
| | | | | | | | Renames `rake test:all` to `rake test` by changing old `rake test:run` to previous version of `rake test:all`. Removes old definition of `rake test`. Also renames `rake test:all:db` to `rake test:db` and deprecates `rake test:all` & `rake test:all:db`
* | Merge pull request #16535 from bf4/patch-1Rafael Mendonça França2014-11-101-0/+6
|\ \ | | | | | | | | | Allow fallback to LegacyKeyGenerator when secret_key_base is not set but secrets.secret_token is
| * | `secret_token` is now saved in `Rails.application.secrets.secret_token`Benjamin Fleischer2014-11-021-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - `secrets.secret_token` is now used in all places `config.secret_token` was - `secrets.secret_token`, when not present in `config/secrets.yml`, now falls back to the value of `config.secret_token` - when `secrets.secret_token` is set, it over-writes `config.secret_token` so they are the same (for backwards-compatibility) - Update docs to reference app.secrets in all places - Remove references to `config.secret_token`, `config.secret_key_base` - Warn that missing secret_key_base is deprecated - Add tests for secret_token, key_generator, and message_verifier - the legacy key generator is used with the message verifier when secrets.secret_key_base is blank and secret_token is set - app.key_generator raises when neither secrets.secret_key_base nor secret_token are set - app.env_config raises when neither secrets.secret_key_base nor secret_token are set - Add changelog Run focused tests via ruby -w -Itest test/application/configuration_test.rb -n '/secret_|key_/'
* | | Add skip-turbolinks entry to 4.2 release notes and improve changelogCarlos Antonio da Silva2014-11-051-1/+1
|/ / | | | | | | [ci skip]
* / Add back --skip-turbolinks and remove --skip-gemsRafael Mendonça França2014-10-261-7/+1
|/ | | | | | | For the most part of cases --skip-gems option just remove one line in the Gemfile. This is not worth for the complexity it adds. Closes #17196
* some changelog formatting. [ci skip]Yves Senn2014-10-161-1/+1
|
* Remove --skip-action-view option from application generatorDan Olson2014-09-241-0/+6
|
* Standardize on `Rails.application` [ci skip]Tamir Duberstein2014-09-191-1/+1
| | | | This seems to be the style settled on in most of the templates.
* Merge pull request #16936 from untidy-hair/plugin_test_db_migrate_pathRafael Mendonça França2014-09-181-0/+6
|\ | | | | | | | | | | | | Specify dummy app's db migrate path in plugin's test_helper.rb Conflicts: railties/CHANGELOG.md
| * Specify dummy app's db migrate path in plugin's test_helper.rbYukio Mizuta2014-09-161-0/+6
| |
* | inject Rack::Lock if config.eager_load is falseXavier Noria2014-09-181-0/+6
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | If code is not eager loaded constants are loaded on demand. Constant autoloading is not thread-safe, so if eager loading is not enabled multi-threading should not be allowed. This showed up in certain Capybara scenarios: Most Capybara drivers other than Rack::Test need a web server. In particular, drivers for JavaScript support. Capybara launches WEBrick in its own thread for those but that per se is fine, because the spec thread and the server thread are coordinated. Problem comes if the page being served in the spec makes Ajax calls. Those may hit WEBrick in parallel, and since WEBrick is multi-threaded and allow_concurrency? returns true in the test environment before this patch, threads are spawned to serve those parallel requests. On the other hand, since eager_load is false by default in the test environment, constants are not preloaded. So the suite is autoloading constants in a multi-threaded set. That's a receipt for paracetamol. The symptom is random obscure errors whose messages point somehow to constant autoloading. As a consequence of this fix for allow_concurrency? WEBrick in Capybara scenarios no longer runs in multi-threaded mode. Fixes #15089.
* Use dynamic path for dummy app location in plugin's test_helper.rbYukio Mizuta2014-09-141-0/+5
|
* Fix spelling. [CI SKIP]Guo Xiang Tan2014-08-271-1/+1
|
* fix broken `gem` method with non-String arguments. Closes #16709.Yves Senn2014-08-271-0/+7
| | | | This was caused by #15327.
* Fix setting simple values to the new config.xCarlos Antonio da Silva2014-08-191-2/+1
| | | | | | | | | | Previously setting simple values to the config.x object resulted in the following: config.x.super_debugger = true config.x.super_debugger #=> {} Which was against the examples showed in the changelog/release notes.
* Revert "Improve custom configuration"Rafael Mendonça França2014-08-191-9/+7
| | | | | | | | | This reverts commit de4891344ccc074f6d5693f4fac6ad610584e336. Conflicts: railties/lib/rails/railtie/configuration.rb It added regression. Will be back after the beta
* Merge pull request #16561 from gsamokovarov/mention-web-console-in-changelogGuillermo Iguaran2014-08-191-0/+7
|\ | | | | Mention web-console in 4.2 release notes
| * Mention web-console in 4.2 release notesGenadi Samokovarov2014-08-201-0/+7
| | | | | | | | | | | | | | | | Mention the web-console inclusion in the default Gemfile in the Release notes and the railties changelog. We can eventually mention it in the upgrade guide, if needed. [ci skip]
* | Improve custom configurationRafael Mendonça França2014-08-191-7/+9
|/ | | | | | | | | | | | | | | | 1. Hashes can be assigned 2. We don't need a special level anymore The method chain only works in the top level. If users need a second level they need to assign a OrderedOptions to the key: config.resque.server = ActiveSupport::OrderedOptions.new config.resque.server.url = "http://localhost" config.resque.server.port = 3000 [Rafael Mendonça França + Carlos Antonio da Silva]
* Add a `required` option to the model generatorSean Griffin2014-08-081-0/+4
| | | | | | | | | | | Syntax was chosen to follow the passing of multiple options to decimal/numeric types. Curly braces, and allowing any of `,`, `.`, or `-` to be used as a separator to avoid the need for shell quoting. (I'm intending to expand this to all columns, but that's another PR. The `required` option will cause 2 things to change. `required: true` will be added to the association. `null: false` will be added to the column in the migration.
* Merge pull request #16359 from skanev/after-bundle-in-rails-templatesYves Senn2014-08-061-0/+7
|\ | | | | | | | | | | | | Add an after_bundle callback in Rails templates Conflicts: railties/CHANGELOG.md
| * Add an after_bundle callback in Rails templatesStefan Kanev2014-08-031-0/+7
| | | | | | | | | | | | The template runs before the generation of binstubs – this does not allow to write one, that makes an initial commit to version control. It is solvable by adding an after_bundle callback.
* | Pull in the custom configuration concept from dhh/custom_configurationDavid Heinemeier Hansson2014-08-031-0/+17
|/
* Merge pull request #16328 from noinkling/template_password_confirmation_fixYves Senn2014-07-291-0/+5
| | | | Give password_confirmation div the "field" class in the scaffold generator "_form" partial
* Add Rails::Application#config_forRafael Mendonça França2014-07-151-0/+18
| | | | | This is a convenience for loading configuration for the current Rails environment.
* Synced 4.2 release notes with the latest commits.Godfrey Chan2014-07-111-1/+1
| | | | | Also reordered some of the items to put newer ones on top (same order as CHANGELOGs), which makes it easier to diff while we are still working on it.
* Change back occurrences of SQLite(3) to sqlite3 when referring to theZachary Scott2014-07-061-1/+1
| | | | adapter, fixed from #16057 [ci skip]
* [ci skip] /sqlite/i --> SQLiteAkshay Vishnoi2014-07-061-1/+1
|
* Deprecate Rails::Rack::LogTailerRafael Mendonça França2014-06-171-0/+4
| | | | | | | | It was being used by Rails for show the development logs but since Rails 4 it is not being used anymore on the framework. This class seems to be private but it were part of the public API we are deprecating before removing.
* Add a generic --skip-gems options to generatorRafael Mendonça França2014-06-171-0/+10
| | | | | | | | | | Also remove --skip-turbolinks. This option is useful if users want to remove some gems like jbuilder, turbolinks, coffee-rails, etc that don't have specific options on the generator. rails new my_app --skip-gems turbolinks coffee-rails
* Emit suggested generator names when not foundschneems2014-06-041-0/+4
| | | | | | | | | | | | | | | When someone types in a generator command it currently outputs all generators. Instead we can attempt to find a subtle mis-spelling by running all generator names through a levenshtein_distance algorithm provided by rubygems. So now a failure looks like this: ```ruby $ rails generate migratioooons Could not find generator 'migratioooons'. Maybe you meant 'migration' or 'integration_test' or 'generator' Run `rails generate --help` for more options. ``` If the suggestions are bad we leave the user with the hint to run `rails generate --help` to see all commands.
* `bin/setup` script to bootstrap applications.Yves Senn2014-05-301-0/+4
|
* Revert "Merge pull request #12778 from etehtsea/rake-default-fix"Yves Senn2014-05-281-4/+0
| | | | | | | | | | | | | This reverts commit ec0a2b57f67c9153cb5f7bbe2a3f66d13fe64bdd, reversing changes made to a8bd7b16260c217290ef8fe3a166fcceac442c62. This reverts commit 555ec36522011862c03b483c53be32410594a51e This reverts commit 555ec36522011862c03b483c53be32410594a51e By default, Rails uses the `default` Rake task to run all tests. This commit changed the environment of the default task to `development`. This clears the development database and has other negative consequences.
* Replace double quotes with single quotes while adding an entry into Gemfilealexbel2014-05-261-0/+4
|
* Future port c8ddb61Zachary Scott2014-05-231-2/+1
|
* Default config.assets.digests to true in developmentDan Kang2014-05-171-0/+4
|
* Use Rails::Paths::Path#existent in database_configurationPier-Olivier Thibault2014-05-071-0/+5
| | | | | | | | | | | | | Database configuration was trying to load the first path that config.paths['config/database'] was returning even if the path didn't exist in the filesystem. Because Rails::Paths::Path has the possibility to return more than 1 path (as an array), database_configuration should filter down the paths to the existing one and then load the first one. This would make it possible to move the database.yml file and add the new path to paths['config/database'] and still load the configurations.
* skip-git should not hit git commands plugin generatorsArun Agrawal2014-05-021-0/+6
|
* Make console and generators blocks works at Application instance levelRafael Mendonça França2014-04-141-0/+6
| | | | | | | Like rake tasks and runner blocks these blocks should also being shared between applications since they are stored at the classes. Fixes #14748
* Move assets precompile (and version) to an initializerMatthew Draper2014-04-111-0/+4
| | | | | sprockets-rails 2.1 needs the precompile list to be available in all environments.
* Add CHANGELOG entry for #12778 [ci skip]Rafael Mendonça França2014-03-281-0/+4
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-10 18:42:51 +0000