aboutsummaryrefslogtreecommitdiffstats
path: root/railties/CHANGELOG.md
Commit message (Collapse)AuthorAgeFilesLines
* support `-` as an argument to `rails runner`Cody Cutrer2017-07-171-0/+5
| | | | | | | | | | | | | in Rails 4.0, you could use `/dev/stdin` on both Linux and Mac, but with the switch to Kernel.load in Rails 4.1, this broke on Linux (you get a LoadError). Instead, explicitly detect `-` as meaning stdin, then read from stdin explicitly, instead of performing file gymnastics. This should now work on any platform uniformly. Passing a script via stdin is useful when you're sshing to a server, and the script you want to run is stored locally. You could theoretically pass the entire script on the command line, but in reality you'll run into problems with the command being too long.
* Add bootsnap to default Gemfile:Burke Libbey2017-07-171-0/+4
| | | | | | Bootsnap precomputes load path resolution and caches ruby ISeq and YAML parsing/compilation, reducing application boot time by approximately 50% on supported configurations.
* Properly expand the environment's nameRobin Dupret2017-07-161-0/+5
| | | | | | | | | Running the `console` and `dbconsole` commands with a regular argument as the environment's name automatically expand it to match an existing environment (e.g. dev for development). This feature wasn't available using the `--environment` (a.k.a `-e`) option.
* Deprecate environment as an argument for dbconsole and consoleRobin Dupret2017-07-161-0/+14
| | | | | | People should rather rely on the `-e` or `--environment` options to specify in which environment they want to work. This will allow us to specify the connection to pick as a regular argument in the future.
* Allow to pass a connection to the `dbconsole` commandRobin Dupret2017-07-161-0/+7
| | | | | | | | | | | Since 0a4f6009, it's possible to specify a 3-level database configuration to gather connections by environment. The `dbconsole` command will try to look for a database configuration which points to the current environment but with such flavour, the environment key is flushed out so let's add the ability to specify the connection and pick `primary` by default to be consistent with Active Record.
* Do not generate unused components contents in `app:update` taskyuuji.yaginuma2017-07-161-0/+7
| | | | | | | | | | | | Currently, `app:update` generates all contents regardless of the component using in application. For example, even if not using Action Cable, `app:update` will generate a contents related to Action Cable. This is a little inconvenient. This PR checks the existence of the component and does not generate unnecessary contents. Can not check all options in this way. However, it will be able to prevent the generation of unnecessary files.
* * Don't eagerly require Rails' minitest plugin.Kasper Timm Hansen2017-07-101-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | By making the Rails minitest behave like a standard minitest plugin we're much more likely to not break when people use other minitest plugins. Like minitest-focus and pride. To do this, we need to behave like minitest: require files up front and then perform the plugin behavior via the at_exit hook. This also saves us a fair bit of wrangling with test file loading. Finally, since the environment and warnings options have to be applied as early as possible, and since minitest loads plugins at_exit, they have to be moved to the test command. * Don't expect the root method. It's likely this worked because we eagerly loaded the Rails minitest plugin and that somehow defined a root method on `Rails`. * Assign a backtrace to failed exceptions. Otherwise Minitest pukes when attempting to filter the backtrace (which Rails' backtrace cleaner then removes). Means the exception message test has to be revised too. This is likely caused by the rails minitest plugin now being loaded for these tests and assigning a default backtrace cleaner.
* Load environment file in `dbconsole` commandyuuji.yaginuma2017-07-091-0/+6
| | | | | | | | | Currently the environment file is not loaded in `dbconsole` command. Therefore, for example, if use encrypted secrets values in database.yml, `read_encrypted_secrets` will not be true, so the value can not be used correctly. Fixes #29717
* Add `rails secrets:show` commandyuuji.yaginuma2017-07-071-0/+4
| | | | | | | | | | | When secrets confirmed with the `secrets:edit` command, `secrets.yml.enc` will change without updating the secrets. Therefore, even if only want to check secrets, the difference will come out. This is a little inconvenient. In order to solve this problem, added the `secrets:show` command. If just want to check secrets, no difference will occur use this command.
* Allow mounting same engine under several locationsDavid Rodríguez2017-07-051-0/+6
|
* Add backticks [ci skip]Ryuta Kamizono2017-07-031-1/+1
|
* Clear screenshots files in `tmp:clear` taskyuuji.yaginuma2017-06-271-0/+4
| | | | | | | | | If system test fails, it creates screenshot under `tmp/screenshots`. https://github.com/rails/rails/blob/34fe2a4fc778d18b7fe6bdf3629c1481bee789b9/actionpack/lib/action_dispatch/system_testing/test_helpers/screenshot_helper.rb#L45 But currently, screenshot files is not cleared by `tmp:clear` task. This patch make clears screenshot files with `tmp:clear` task as well as other tmp files.
* Add `railtie.rb` to the plugin generatorTsukuru Tanimichi2017-06-261-0/+4
|
* Deprecate an `capify!` method in generators and templatesyuuji.yaginuma2017-06-181-0/+4
| | | | | | | | | The `capify` command has been removed by Capistrano 3 and became to `cap install`. Therefore, the `capify!` method has no meaning in Capistrano 3. I think that should deprecate. Ref: https://github.com/capistrano/capistrano/commit/492793916acf32ffe1604daec6fd4892c8935018
* Allow irb options to be passed from `rails console` commandyuuji.yaginuma2017-05-081-0/+6
| | | | Fixes #28988
* Cleanup CHANGELOGs [ci skip]Ryuta Kamizono2017-04-301-1/+0
| | | | | | * Remove trailing spaces. * Add backticks around method and command. * Fix indentation.
* Added a shared section to config/database.yml that will be loaded for all ↵Pierre Schambacher2017-04-261-3/+7
| | | | environments
* Namespace CSS selectors on error pagesJan Krutisch2017-04-201-0/+7
| | | | The css selectors on the generated error pages are too broad (for example `text-align: center` on `body` and thus bleed out to the following pages (say, by pressing the back button) when using Turbolinks. This commit namespaces all the selectors.
* No need to duplicate 5-1-stable CHANGELOG. [ci skip]Yves Senn2017-03-281-8/+0
| | | | | | The `master` changelog refer back to the `5-1-stable` changelog as a base. No need to duplicate backported entries in the changelogs on `master`.
* minor CHANGELOG formatting changes. [ci skip]Yves Senn2017-03-261-3/+2
|
* add field ids when generating a scaffold form.Yves Senn2017-03-261-0/+9
| | | | | | This is a follow up to a6d065e. When using `form_with` you must supply field ids manually. Since the scaffold generator is using labels we need to make sure that they are linked up properly.
* Start Rails 5.2 developmentMatthew Draper2017-03-221-199/+1
|
* Remove 5.0.0 entry from 5.1.0 CHANGELOG [ci skip]claudiob2017-03-201-4/+0
| | | | | | | | | | | The entry for PR #25430 is currently present both in the CHANGELOG for Rails 5.0 and for Rails 5.1: https://github.com/rails/rails/blame/9d3a352777c2594123583b0bc02d0dd80f1e385b/railties/CHANGELOG.md#L61-L72 Since the PR was backported to 5-0-stable in #25499, I believe it should be removed from the CHANGELOG of 5.1, otherwise it looks like something changed from 5.0 to 5.1
* Add `app:update` task to enginesyuuji.yaginuma2017-03-201-0/+4
| | | | | | Occasionally we update the file generated by engine. Therefore, I think that there is a task for updating as well as application in the engine, it is convenient for updating.
* Add CHANGELOG entry for --skip-coffee [ci skip]claudiob2017-03-141-0/+4
| | | | Was added in #25248 by @bluesh55
* Move "fixes" to a new lineJon Moss2017-03-131-1/+3
| | | | [ci skip]
* [ci skip] 🎬 expensive: take twoKasper Timm Hansen2017-03-061-1/+1
|
* Avoid running system tests by defaultRobin Dupret2017-03-051-0/+5
| | | | | | | | | | These tests may be expansive so let's only allow users to run them through `bin/rails test:system` or by passing a path to the `test` command. The same applies for `bin/rake test`. Refs #28109.
* [ci skip] Add changelog entry for #28139.Kasper Timm Hansen2017-03-021-0/+16
| | | | Includes a script to ease an app's upgrade.
* [ci skip] Add changelog entry for encrypted secrets.Kasper Timm Hansen2017-03-011-0/+14
| | | | Just dispatch to the command help itself for more info.
* Preparing for 5.1.0.beta1 releaseRafael Mendonça França2017-02-231-0/+2
|
* Revert back to the original of using package.json in the root of the project ↵David Heinemeier Hansson2017-02-211-1/+1
| | | | (#28093)
* Collect all file patterns when running multiple rake test tasksDominic Cleal2017-02-041-0/+6
| | | | | | | Replaces the rake_patterns instance variable with simple require, as `autorun` will run tests from all eagerly required test files. Fixes #27801
* add warnings option to test runneryuuji.yaginuma2017-01-241-0/+4
|
* Merge pull request #27632 from dixpac/repo_initializeRafael Mendonça França2017-01-181-0/+5
|\ | | | | | | Initalize git repo when creatin new rails app
| * Initalize git repo when creatin new rails appdixpac2017-01-121-0/+5
| | | | | | | | | | * If `--skip-git` is not specified initalize git repo when creating new rails app
* | Install Byebug gem as default in Windows (mingw and x64_mingw) platform.Junichi Ito2017-01-181-0/+4
| |
* | make all rails commands work in engineyuuji.yaginuma2017-01-091-0/+4
|/ | | | | | | | Currently, all rails commands can be executed in engine, but `server`, `console`, `dbconsole` and `runner` do not work. This make all rails commands work in engine. Related to #22588
* Don't generate HTML/ERB templates for scaffold controller with --api flagPrathamesh Sonpatki2017-01-071-0/+6
| | | | - Fixes #27591.
* Merge pull request #27399 from sinogermany/rails-env-for-empty-string-env-varsRafael Mendonça França2017-01-031-0/+4
|\ | | | | | | Rails env for empty string env vars
| * Rails.env falls back to dev mode when env var is emptyDaniel Deng2017-01-041-0/+4
| |
* | Remove deprecated CONTROLLER environment variable for routes taskRafael Mendonça França2017-01-031-0/+4
| |
* | Remove deprecated tasks in railtiesRafael Mendonça França2017-01-031-0/+5
| |
* | Remove deprecated file `rails/rack/debuggerRafael Mendonça França2017-01-031-0/+4
| |
* | Remove deprecated config.serve_static_filesRafael Mendonça França2017-01-031-0/+4
| |
* | Remove deprecated `config.static_cache_control`Rafael Mendonça França2017-01-031-1/+5
| |
* | Merge branch 'master' into clear_all_environments_log_by_defaultRafael França2016-12-291-0/+31
|\ \
| * | Add backticks to show shell commandJon Moss2016-12-271-2/+2
| | | | | | | | | | | | [ci skip]
| * | Remove random extra spaces from Action Pack and Railties CHANGELOG.mdJon Moss2016-12-271-2/+2
| |/ | | | | | | [ci skip]
| * Add option to trigger JS framework-specific installation as part of webpack ↵David Heinemeier Hansson2016-12-121-0/+12
| | | | | | | | setup
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-27 18:11:17 +0000