aboutsummaryrefslogtreecommitdiffstats
path: root/railties/CHANGELOG.md
Commit message (Collapse)AuthorAgeFilesLines
...
* pass over CHANGELOGs. [ci skip]Yves Senn2015-04-221-8/+10
|
* Fix typos and improve the documentationJon Atack2015-04-151-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a squash of the following commits, from first to last: - Fix minor, random things I’ve come across lately that individually did not seem worth making a PR for, so I saved them for one commit. One common error is using “it’s” (which is an abbreviation of “it is”) when the possessive “its” should be used for indicating possession. - Changes include the name of a test, so remove the `[skip ci]` (thanks @senny). - Line wrap the changes at 80 chars and add one more doc fix. - Add a missing line wrap in the Contributing to Ruby on Rails Guide. - Line wrap the `TIP` section in the Contributing to Ruby on Rails Guide as well. Rendering the guide locally with `bundle exec rake guides:generate` did not show any change in on-screen formatting after adding the line wrap. The HTML generated is (extra line added to illustrate where the line wrap takes place): <div class="info"><p>Please squash your commits into a single commit when appropriate. This simplifies future cherry picks and also keeps the git log clean.</p></div> - Squash commits.
* :scissors:Zachary Scott2015-04-121-2/+2
|
* Rename railties/bin to railties/exeIslam Wazery2015-04-111-0/+4
| | | | | | That will match the new Bundler executables convention. Bundler Blog Post: http://bundler.io/blog/2015/03/20/moving-bins-to-exe.html Also updated the necessary tests.
* Merge pull request #19429 from mxhold/print_bundle_install_output_line_by_lineMatthew Draper2015-04-031-0/+7
|\ | | | | | | Print `bundle install` output in `rails new` as soon as it's available
| * Print `bundle install` output in `rails new` as soon as it's availableMax Holder2015-03-281-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, running `rails new` would not print any of the output from `bundle install` until all the gems had finished installing. This made it look like the generator was hanging at the `bundle install` step. This commit switches to using `system` so that the bundle command can output as it needs to. This has the added benefit of including output bundler produces on standard error, which the previous code ignored since backticks only capture standard out. This is not a big deal right now since bundler does not currently print errors to standard error, but that may change in the future (see: bundler/bundler/issues/3353).
* | Improve CHANGELOG for fix for respecting pluralize_table_names [ci skip]Prathamesh Sonpatki2015-03-271-1/+1
| |
* | respect `pluralize_table_names` when generate fixture file. fixes #19519yuuji.yaginuma2015-03-271-0/+6
| |
* | Fix typo in belongs_to_required_by_default config's CHANGELOG entry [ci skip]Prathamesh Sonpatki2015-03-221-1/+1
|/
* `rake initializer` -> `rake initializers`Godfrey Chan2015-03-201-4/+5
| | | | | | Also edited the copy to be more consistent with `rake routes`. See #19323.
* Revert "Merge pull request #19411 from dmathieu/rack_env_changelog"Jeremy Kemper2015-03-201-7/+0
| | | | | | | Preserving RACK_ENV behavior. This reverts commit b19990c82c6a9beff0cd058dc2ff67894a2f9ea7, reversing changes made to ac291b76ea770b5795c767f2f74a8d0b33744809.
* add changelog entry for removing the fallback to rack_envDamien Mathieu2015-03-191-0/+7
| | | | [ci skip]
* Add a new-line to the end of route method generated code.Arthur Neves2015-03-181-0/+7
| | | | | | | | Fix regression on route method that was added by bac812a7ef2660a2fe2ab00822e5e66228379822. The regression was that when calling the `route` method, we were not appending a \n anymore. [fixes #19316]
* Add `rake initializer`Naoto Kaneko2015-03-141-0/+7
| | | | | This task prints out initializers for an application. It is useful to develop a rubygem which involves the initialization process.
* Revert "Merge pull request #15476 from JacobEvelyn/master"Jeremy Kemper2015-03-111-7/+0
| | | | | | | | | | | | | | | | This introduces undesirable `Rails.logger` formatters (such as the syslog formatter) onto a `Logger.new(STDERR)` for the console. The production logger may be going elsewhere than standard io, so we can't presume to reuse its formatter. With syslog, this causes missing newlines in the console, so irb prompts start at the end of the last log message. We can work to expose the console formatter in another way to address the original issue. This reverts commit 026ce5ddf11c4cda0aae7f33a9266e54117db318, reversing changes made to 6f0a69c5899ebdc892e2aa23e68e2604fa70fb73.
* Created rake restart task.Hyonjee Joo2015-02-261-0/+7
| | | | | | Fixes #18876. Rake restart touches `tmp/restart.txt` to restart application on next request. Updated tests and documentation accordingly.
* Merge pull request #15476 from JacobEvelyn/masterRafael Mendonça França2015-02-251-0/+7
|\ | | | | | | Use logger environment settings in Rails console.
* | Require `belongs_to` by default.Josef Šimánek2015-02-211-0/+15
| | | | | | | | Deprecate `required` option in favor of `optional` for belongs_to.
* | Allow Rack::Runtime to be deleted from middleware stack.Guo Xiang Tan2015-02-191-0/+8
| | | | | | | | Fixes: https://github.com/rails/rails/issues/16433.
* | README.rdoc -> README.md for newly generated applicationsXavier Noria2015-02-061-0/+4
| | | | | | | | | | | | README.rdoc was generated to support the doc:app task. Now that this task is gone we can switch to Markdown, which is nowadays a better default.
* | Remove documentation tasksXavier Noria2015-02-061-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch removes the tasks doc:app, doc:rails, and doc:guides. In our experience applications do not generate APIs using doc:app. Methods may be certainly documented for maintainers, annotated with YARD tags, etc. but that is intended to be read with the source code, not in a separate website. Then, teams also have typically selected topics written down in Markdown files, or in a GitHub wiki... that kind of thing. If a team absolutely needs to generate application documentation for internal purposes, they can still easily write their own task. Regarding doc:rails and doc:guides, we live in 2015. We are used to go to online docs all the time. If you really want access to the API offline RubyGems generates it for every Rails component unless you tell it not to, and you can checkout the Rails source code to read the guides as Markdown, or download them for a Kindle reader. All in all, maintaining this code does not seem to be worthwhile anymore. As a consequence of this, guides (+3 MB uncompressed) won't be distributed with the rails gem anymore. Of course, guides and API are going to be still part of releases, since documentation is maintained alongside code and tests. Also, time permitting, this will allow us to experiment with novel ways to generate documentation in the Rails docs server, since right now we were constrained by being able to generate them in the user's environment.
* | Force generated route to be insertedAndrew White2015-02-051-0/+4
| | | | | | | | | | | | | | Thor isn't very discerning over whether some content is present when passed to `inject_into_file`, e.g. a commented out route is detected as being present. So to prevent people scratching their heads as to why a route hasn't appeared it's better to fall on the side of having duplicate routes.
* | Don't remove all line endings from routes.rbAndrew White2015-02-031-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | When there is a single scaffold in the routes.rb with no other lines then revoking/destroying it will create a routes.rb file with a syntax error. This is because the sentinel for the Thor `route` action didn't include the newline but the logged route code did. The fix is to add the newline to the sentinel and remove it from the the logged route code. Fixes #15913.
* | Update option to skip test in generatorsMelanie Gilman2015-01-271-0/+4
| | | | | | | | Rails no longer generates Test::Unit files by default.
* | Add the `method_source` gem to the default GemfileSean Griffin2015-01-131-0/+4
| | | | | | | | Fixes #18473
* | Drop old test locations from `rake stats`brainopia2015-01-091-0/+6
| | | | | | | | | | - test/functional - test/unit
* | Update `rake counts` to count declarative tests in minitestbrainopia2015-01-091-0/+5
| |
* | Fix CHANGELOG [ci skip]Rafael Mendonça França2015-01-041-0/+2
| |
* | Remove deprecated `test:all` and `test:all:db` tasksRafael Mendonça França2015-01-041-0/+2
| |
* | Remove deprecated `Rails::Rack::LogTailer`Rafael Mendonça França2015-01-041-0/+4
| |
* | Remove deprecated `RAILS_CACHE` constantRafael Mendonça França2015-01-041-0/+4
| |
* | Remove deprecated `serve_static_assets` configurationRafael Mendonça França2015-01-041-0/+4
| |
* | Merge pull request #13434 from tanraya/local_variablesCarlos Antonio da Silva2015-01-031-0/+4
|\ \ | | | | | | | | | | | | | | | | | | Use local variables in _form.html.erb generated by scaffold. Conflicts: railties/CHANGELOG.md
| * | Use local variables in _form.html.erb generated by scaffold generator.tanraya2014-07-261-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It seems a good idea to use local variables in generated partials instead of using instance variables. Before <%= render 'form' %> After <%= render 'form', product: @product %>
* | | Merge pull request #17227 from claudiob/explicitly-abort-callbacksRafael Mendonça França2015-01-031-0/+15
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | Introduce explicit way of halting callback chains by throwing :abort. Deprecate current implicit behavior of halting callback chains by returning `false` in apps ported to Rails 5.0. Completely remove that behavior in brand new Rails 5.0 apps. Conflicts: railties/CHANGELOG.md
| * | | Add config to halt callback chain on return falseclaudiob2015-01-021-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This stems from [a comment](rails#17227 (comment)) by @dhh. In summary: * New Rails 5.0 apps will not accept `return false` as a way to halt callback chains, and will not display a deprecation warning. * Existing apps ported to Rails 5.0 will still accept `return false` as a way to halt callback chains, albeit with a deprecation warning. For this purpose, this commit introduces a Rails configuration option: ```ruby config.active_support.halt_callback_chains_on_return_false ``` For new Rails 5.0 apps, this option will be set to `false` by a new initializer `config/initializers/callback_terminator.rb`: ```ruby Rails.application.config.active_support.halt_callback_chains_on_return_false = false ``` For existing apps ported to Rails 5.0, the initializers above will not exist. Even running `rake rails:update` will not create this initializer. Since the default value of `halt_callback_chains_on_return_false` is set to `true`, these apps will still accept `return true` as a way to halt callback chains, displaying a deprecation warning. Developers will be able to switch to the new behavior (and stop the warning) by manually adding the line above to their `config/application.rb`. A gist with the suggested release notes to add to Rails 5.0 after this commit is available at https://gist.github.com/claudiob/614c59409fb7d11f2931
* | | | Merge pull request #18309 from PaBLoX-CL/fix-fixtures-referencesRafael Mendonça França2015-01-021-0/+4
|/ / / | | | | | | | | | | | | Generated fixtures won't use parent_id when generated with parent:references
* | | Add --skip-action-mailer (or -M) to rails generateclaudiob2015-01-011-0/+4
| | |
* | | 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_/'
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-02 04:21:02 +0000