aboutsummaryrefslogtreecommitdiffstats
path: root/railties/lib/rails
Commit message (Collapse)AuthorAgeFilesLines
* Fix rubocop offencesRyuta Kamizono2019-04-301-1/+1
|
* new config to opt-out from adding app directories to $LOAD_PATHXavier Noria2019-04-282-6/+10
|
* Bump bootsnap to a version with disables iseq_cache for Ruby 2.5Prathamesh Sonpatki2019-04-261-1/+1
| | | | - Refs https://github.com/Shopify/bootsnap/pull/257
* Start Rails 6.1 developmentRafael Mendonça França2019-04-242-2/+4
|
* Merge pull request #36067 from st0012/update-generator-for-api-appRafael França2019-04-232-0/+4
|\ | | | | Remove action_controller.perform_caching from api app's configs
| * Remove action_controller.perform_caching from api app's configsst00122019-04-242-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | As suggested in https://github.com/rails/rails/issues/35602#issuecomment-485833483, because we don't provide view caching and doesn't include `ActionController::Caching` for api apps, we should also avoid generating ```ruby config.action_controller.perform_caching = true ``` for those api apps. So it won't confuse people. **But because `perform_caching` will be `true` if not set, the behavior of the app would still be the same without these configs.**
* | Merge pull request #35852 from larouxn/resurrectionRafael França2019-04-232-0/+9
|\ \ | |/ |/| Resurrect external JS/CS generation
| * Burn unnecessary files 🔥Nicholas La Roux2019-04-053-19/+0
| |
| * Style fixesNicholas La Roux2019-04-051-3/+3
| |
| * Resurrect generator templatesNicholas La Roux2019-04-052-0/+4
| |
| * Resurrect js/js engine options and generatorsNicholas La Roux2019-04-053-0/+24
| |
* | Implements the task zeitwerk:checkXavier Noria2019-04-232-0/+79
| | | | | | | | [Matilda Smeds & Xavier Noria]
* | Allow sass-rails greater than 5.x in new appsGuillermo Iguaran2019-04-221-1/+1
| |
* | [#35782] Allow loading seeds without ActiveJob (~> 5.2.3)Jeremy Weathers2019-04-191-1/+1
| |
* | Add `null: false` constraint by default for `belongs_to` associationsPrathamesh Sonpatki2019-04-191-2/+8
| | | | | | | | | | | | - Also deprecate passing {required} to the model generator. - Also made sure the global config `belongs_to_required_by_default` is applied correctly to the model generator for `null: false` option.
* | Merge pull request #34788 from gsamokovarov/actionable-errorsKasper Timm Hansen2019-04-191-0/+1
|\ \ | | | | | | Introduce Actionable Errors
| * | Manage ActionDispatch::ActionableExceptions from the default middleware stackGenadi Samokovarov2019-04-191-0/+1
| | |
* | | Help command for visible commands should be hiddenakinomaeni2019-04-191-2/+4
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ``` $ rails --help > tmp/before $ bundle update rails ... $ rails --help > tmp/after $ diff -u tmp/before tmp/after --- tmp/before 2019-04-19 00:12:08.000000000 -0700 +++ tmp/after 2019-04-19 00:14:55.000000000 -0700 @@ -52,7 +52,6 @@ db:version destroy dev:cache - dev:help encrypted:edit encrypted:show initializers ```
* | Factorize bin/update in bin/setup, and make bin/setup idempotentDavid Stosik2019-04-172-35/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `bin/setup` and `bin/update` are currently almost the same file. The only thing that keeps them apart is that one is running `bin/rails db:setup` and the other `bin/rails db:migrate`. I'm suggesting here that they should be a unique script, which needs to be idempotent. - New to a project, need to get started? `bin/setup` - Need to install new dependencies that were added recently? `bin/setup`. Before deprecating `bin/update`, I'm suggesting we just have it call `bin/setup`.
* | Add collection cache versioningLachlan Sylvester2019-04-161-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Cache versioning enables the same cache key to be reused when the object being cached changes by moving the volatile part of the cache key out of the cache key and into a version that is embedded in the cache entry. This is already occurring when the object being cached is an `ActiveRecord::Base`, but when caching an `ActiveRecord::Relation` we are currently still putting the volatile information (max updated at and count) as part of the cache key. This PR moves the volatile part of the relations `cache_key` into the `cache_version` to support recycling cache keys for `ActiveRecord::Relation`s.
* | [Rails::MailersController] Do not leak I18n global setting changesThierry Joyal2019-04-161-2/+5
| |
* | Merge pull request #35906 from yoones/notes-tags-registrationRafael França2019-04-152-2/+15
|\ \ | | | | | | Notes tags registration
| * | Adds `register_tags`Younes SERRAJ2019-04-122-2/+15
| | |
* | | generate config.cache_classes = false if SpringXavier Noria2019-04-141-5/+10
| | |
* | | deprecates autoloading constants during initialization [closes #35745]Xavier Noria2019-04-141-0/+37
| | | | | | | | | | | | See rationale in the warning message included in the patch.
* | | Do not treat `environment_desc` as commandsyuuji.yaginuma2019-04-131-1/+3
| | | | | | | | | | | | For avoid to show `environment_desc` in help.
* | | Merge pull request #35916 from soartec-lab/delete_not_use_methodRyuta Kamizono2019-04-111-15/+0
|\ \ \ | |/ / |/| | Delete not user method for plugin_generator
| * | Delete not user method for plugin_generatorsoartec-lab2019-04-091-15/+0
| | |
* | | Only override async adapter when seedingBatedUrGonnaDie2019-04-091-1/+7
|/ /
* / depend on Zeitwerk 2Xavier Noria2019-04-071-1/+1
|/
* Use `execute_batch2` rather than `execute_batch` to fix performance ↵Ryuta Kamizono2019-04-041-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | regression for fixture loading d8d6bd5 makes fixture loading to bulk statements by using `execute_batch` for sqlite3 adapter. But `execute_batch` is slower and it caused the performance regression for fixture loading. In sqlite3 1.4.0, it have new batch method `execute_batch2`. I've confirmed `execute_batch2` is extremely faster than `execute_batch`. So I think it is worth to upgrade sqlite3 to 1.4.0 to use that method. Before: ``` % ARCONN=sqlite3 bundle exec ruby -w -Itest test/cases/associations/eager_test.rb -n test_eager_loading_too_may_ids Using sqlite3 Run options: -n test_eager_loading_too_may_ids --seed 35790 # Running: . Finished in 202.437406s, 0.0049 runs/s, 0.0049 assertions/s. 1 runs, 1 assertions, 0 failures, 0 errors, 0 skips ARCONN=sqlite3 bundle exec ruby -w -Itest -n test_eager_loading_too_may_ids 142.57s user 60.83s system 98% cpu 3:27.08 total ``` After: ``` % ARCONN=sqlite3 bundle exec ruby -w -Itest test/cases/associations/eager_test.rb -n test_eager_loading_too_may_ids Using sqlite3 Run options: -n test_eager_loading_too_may_ids --seed 16649 # Running: . Finished in 8.471032s, 0.1180 runs/s, 0.1180 assertions/s. 1 runs, 1 assertions, 0 failures, 0 errors, 0 skips ARCONN=sqlite3 bundle exec ruby -w -Itest -n test_eager_loading_too_may_ids 10.71s user 1.36s system 95% cpu 12.672 total ```
* Don't normalize `original_app_name`Ryuta Kamizono2019-04-031-2/+2
| | | | | `original_app_name` is used to show error message if giving app name is invalid, it should be shown raw app name.
* Merge pull request #35805 from excid3/attachments-field-generatorsRafael França2019-04-027-20/+51
|\ | | | | Add attachment and attachments field generators
| * Add attachment and attachments field generatorsChris Oliver2019-03-307-20/+51
| |
* | Rename `connection` option to `database` in `dbconsole` commandyuuji.yaginuma2019-04-021-7/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We introduced `connection` option for specifying spec with 1acd9a6464668d4d54ab30d016829f60b70dbbeb. But now we are using the `database` to specify the same value in other commands. * https://github.com/rails/rails/blob/0a0f115031b64b5335fa88543c40df4194dfb428/activerecord/lib/rails/generators/active_record/migration/migration_generator.rb#L11 * https://github.com/rails/rails/blob/0a0f115031b64b5335fa88543c40df4194dfb428/activerecord/lib/rails/generators/active_record/model/model_generator.rb#L17 The options provided to the users should be uniform. Since the term "database" is used in rake task etc, So I want to be able to use it in `dbconsole` command. Also I deprecated the `connection` option because I think that it would be confusing if there are multiple options to specify a same value.
* | Merge pull request #35820 from sharang-d/url-to-URL-except-actionpackRyuta Kamizono2019-04-021-4/+4
|\ \ | | | | | | url -> URL where apt except inside actionpack/
| * | url -> URL where apt except inside actionpack/Sharang Dashputre2019-04-011-4/+4
| | |
* | | Include final newline in generated .ruby-versionOrhan Toy2019-04-011-1/+1
|/ /
* | optimizes eager loading in :zeitwerk modeXavier Noria2019-03-301-22/+9
| | | | | | | | | | | | | | | | | | | | | | During initialization, the eager load paths of engines are unshifted into AS::Dependencies.autoload_paths. After that, the collection is frozen. (See the initializers in railties/lib/rails/engine.rb.) Hence, there is no eager load path that is not an autoload path too, and so the array difference in the deleted code is always an empty array. Just do nothing.
* | fixes eager loading edge case in :zeitwerk modeXavier Noria2019-03-301-2/+5
|/
* Add rich_text field to model generatorsChris Oliver2019-03-282-10/+19
|
* bumps Zeitwerk and BootsnapXavier Noria2019-03-261-1/+1
|
* Merge pull request #35732 from rails/webdriversGuillermo Iguaran2019-03-241-2/+2
|\ | | | | Replace chromedriver-helper with webdrivers
| * Use webdrivers instead of chromedriver-helper in new appsGuillermo Iguaran2019-03-241-2/+2
| |
* | Merge pull request #35723 from sikachu/disable-sandbox-flagGuillermo Iguaran2019-03-242-1/+9
|\ \ | |/ |/| Add config.disable_sandbox option to Rails console
| * Add config.disable_sandbox option to Rails consolePrem Sichanugrist2019-03-232-1/+9
| | | | | | | | | | | | | | | | | | | | | | A long-running `rails console --sandbox` could cause a database server to become out-of-memory as it's holding on to changes that happen on the database. Given that it's common for Ruby on Rails application with huge traffic to have separate write database and read database, we should allow the developers to disable this sandbox option to prevent someone from accidentally causing the Denial-of-Service on their server.
* | Merge pull request #35718 from ↵Yuji Yaginuma2019-03-241-1/+12
|\ \ | | | | | | | | | | | | y-yagi/add_secret_key_base_when_creating_new_credentials Add `secret_key_base` when creating new credential file
| * | Add `secret_key_base` when creating new credential fileyuuji.yaginuma2019-03-231-1/+12
| |/ | | | | | | | | | | | | | | Since `secret_key_base` is expected to be included in credential file, `secret_key_base` should be included even if re-create the file. This is the same behavior as creating a new app. When env is specified, it may be unnecessary, so I added it only when not specifying env.
* / Update comment for how secret key is calculatedJohn Hawthorn2019-03-221-1/+2
|/ | | | | | | This updates the comment to reflect how the secret key is generated since 4c743587ad6a31908503ab317e37d70361d49e66 Fixes #35717
* Use symbol for mail preview format, not stringJohn Hawthorn2019-03-181-1/+1
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-01-01 06:37:21 +0000