RubyGems - railties - Versions diffs - 5.1.7 → 5.2.0.beta1 - Mend

railties 5.1.7 → 5.2.0.beta1

Files changed (266) hide show

checksums.yaml CHANGED

@@ -1,7 +1,7 @@
 ---
-SHA256:
-  metadata.gz: 759d28481e93ea3ecb64f7a58746c520b8862167453ba27f1efbeff710a6bbb4
-  data.tar.gz: afcd51a61e52b7bd1e5e179f744f2062121a435d8a0b8841536481eeb7c5215b
+SHA1:
+  metadata.gz: fe2084c59562318f868ebadda47eddfc963e86d8
+  data.tar.gz: 0ecd6b7659958fe062acb87c4ea498a13cc5350a
 SHA512:
-  metadata.gz: ad44a2d0815a0bac638ecf79727437a27ebb3e80d2187fa293bcc8e3972c39dd23288da85975dd8be918162de531e1afbbb5911562d295c1a0a12793bc311f01
-  data.tar.gz: 5e1ed3df6d86891fc66662eff9a90a6709340039a1620c4f8b8ef78804af261487be795d17f86c764417b9fcbafd9e1d48937414d9fe7b71fbf1365056a564c6
+  metadata.gz: 0035eff10d9ef03c44ad7759f5e3eec938a66b16987be2a41a27ff85480030024f3228911a0a329ad10093927ce461a91e5d39489af8f68dd0c49b5b5cade0e6
+  data.tar.gz: 543917a45751774ad595d761db7409822516169d42e13ca61ffcfe700d868823588eacf5679fa7af4ff8a21d18c10c5fc1c8e7d21b20a7ccbe968c1921e38315

data/CHANGELOG.md CHANGED

@@ -1,323 +1,159 @@
-## Rails 5.1.7 (March 27, 2019) ##
+## Rails 5.2.0.beta1 (November 27, 2017) ##
-*   No changes.
+*   Deprecate `after_bundle` callback in Rails plugin templates.
+    *Yuji Yaginuma*
-## Rails 5.1.6.2 (March 11, 2019) ##
-*   No changes.
-## Rails 5.1.6.1 (November 27, 2018) ##
-*   No changes.
-## Rails 5.1.6 (March 29, 2018) ##
-*   Fix check for minimum Ruby version to correctly identify Ruby 2.2.10.
-    *shia*
-*   Fix minitest rails plugin.
-    The custom reporters are added only if needed.
-    This will fix conflicts with others plugins.
-    *Kevin Robatel*
+*   `rails new` and `rails plugin new` get `Active Storage` by default.
+     Add ability to skip `Active Storage` with `--skip-active-storage`
+     and do so automatically when `--skip-active-record` is used.
-## Rails 5.1.5 (February 14, 2018) ##
+    *bogdanvlviv*
 *   Gemfile for new apps: upgrade redis-rb from ~> 3.0 to 4.0.
     *Jeremy Daer*
+*   Add `mini_magick` to default `Gemfile` as comment.
-## Rails 5.1.4 (September 07, 2017) ##
+    *Yoshiyuki Hirano*
-*   No changes.
+*   Derive `secret_key_base` from the app name in development and test environments.
+    Spares away needless secret configs.
-## Rails 5.1.4.rc1 (August 24, 2017) ##
+    *DHH*, *Kasper Timm Hansen*
-*   Allow irb options to be passed from `rails console` command.
+*   Support multiple versions arguments for `gem` method of Generators.
-    Fixes #28988.
-    *Yuji Yaginuma*
-## Rails 5.1.3 (August 03, 2017) ##
+    *Yoshiyuki Hirano*
-*   No changes.
+*   Add `--skip-yarn` option to the plugin generator.
+    *bogdanvlviv*
-## Rails 5.1.3.rc3 (July 31, 2017) ##
+*   Optimize routes indentation.
-*   No changes.
+    *Yoshiyuki Hirano*
+*   Optimize indentation for generator actions.
-## Rails 5.1.3.rc2 (July 25, 2017) ##
+    *Yoshiyuki Hirano*
-*   Regression fix: Allow `bin/rails test` to take absolute paths to tests.
+*   Skip unused components when running `bin/rails` in Rails plugin.
-    *Pawan Dubey*
+    *Yoshiyuki Hirano*
-## Rails 5.1.3.rc1 (July 19, 2017) ##
+*   Add `git_source` to `Gemfile` for plugin generator.
-*   Make Rails' test runner work better with minitest plugins.
-    By demoting the Rails test runner to just another minitest plugin —
-    and thereby not eager loading it — we can co-exist much better with
-    other minitest plugins such as pride and minitest-focus.
+    *Yoshiyuki Hirano*
-    *Kasper Timm Hansen*
+*   Add `--skip-action-cable` option to the plugin generator.
-*   Load environment file in `dbconsole` command.
+    *bogdanvlviv*
-    Fixes #29717
+*   Deprecate support of use `Rails::Application` subclass to start Rails server.
     *Yuji Yaginuma*
-*   Allow mounting the same engine several times in different locations.
+*   Add `ruby x.x.x` version to `Gemfile` and create `.ruby-version`
+    root file containing the current Ruby version when new Rails applications are
+    created.
-    Fixes #20204.
+    *Alberto Almagro*
-    *David Rodríguez*
+*   Support `-` as a platform-agnostic way to run a script from stdin with
+    `rails runner`
+    *Cody Cutrer*
-## Rails 5.1.2 (June 26, 2017) ##
+*   Add `bootsnap` to default `Gemfile`.
-*   Add Windows support to `rails secrets:edit`.
-    *Kasper Timm Hansen*
-## Rails 5.1.1 (May 12, 2017) ##
-*   No changes.
+    *Burke Libbey*
+*   Properly expand shortcuts for environment's name running the `console`
+    and `dbconsole` commands.
-## Rails 5.1.0 (April 27, 2017) ##
+    *Robin Dupret*
-*   Namespace error pages' CSS selectors to stop the styles from bleeding into other pages
-    when using Turbolinks.
+*   Passing the environment's name as a regular argument to the
+    `rails dbconsole` and `rails console` commands is deprecated.
+    The `-e` option should be used instead.
-    *Jan Krutisch*
+    Previously:
-*   Raise a error when using a bad symlink
+        $ bin/rails dbconsole production
-    Previously bad symlinks (where the link destination doesn't exist)
-    would be silent ignored and lead to hard to diagnose problems as
-    the non-existence isn't readily apparent.
+    Now:
-    *Richard Schneeman*
+        $ bin/rails dbconsole -e production
-*   Remove -j (--javascript) option from `rails new` command.
+    *Robin Dupret*, *Kasper Timm Hansen*
-    *claudiob*
+*   Allow passing a custom connection name to the `rails dbconsole`
+    command when using a 3-level database configuration.
-*   Specify form field ids when generating a scaffold.
+        $ bin/rails dbconsole -c replica
-    This makes sure that the labels are linked up with the fields. The
-    regression was introduced when the template was switched to
-    `form_with`.
+    *Robin Dupret*, *Jeremy Daer*
-    *Yves Senn*
+*   Skip unused components when running `bin/rails app:update`.
-*   Add `app:update` task to engines.
+    If the initial app generation skipped Action Cable, Active Record etc.,
+    the update task honors those skips too.
     *Yuji Yaginuma*
-*   Avoid running system tests by default with the `bin/rails test`
-    and `bin/rake test` commands since they may be expensive.
-    Fixes #28286.
-    *Robin Dupret*
-*   Improve encryption for encrypted secrets.
-    Switch to aes-128-gcm authenticated encryption. Also generate a random
-    initialization vector for each encryption so the same input and key can
-    generate different encrypted data.
-    Double the encryption key entropy by properly extracting the underlying
-    bytes from the hexadecimal seed key.
-    NOTE: Since the encryption mechanism has been switched, you need to run
-    this script to upgrade:
-    https://gist.github.com/kaspth/bc37989c2f39a5642112f28b1d93f343
-    *Stephen Touset*
-*   Add encrypted secrets in `config/secrets.yml.enc`.
-    Allow storing production secrets straight in the revision control system by
-    encrypting them.
-    Use `bin/rails secrets:setup` to opt-in by generating `config/secrets.yml.enc`
-    for the secrets themselves and `config/secrets.yml.key` for the encryption key.
-    Edit secrets with `bin/rails secrets:edit`.
+*   Make Rails' test runner work better with minitest plugins.
-    See `bin/rails secrets:setup --help` for more.
+    By demoting the Rails test runner to just another minitest plugin —
+    and thereby not eager loading it — we can co-exist much better with
+    other minitest plugins such as pride and minitest-focus.
     *Kasper Timm Hansen*
-*   Fix running multiple tests in one `rake` command
-    e.g. `bin/rake test:models test:controllers`
-    *Dominic Cleal*
+*   Load environment file in `dbconsole` command.
-*   Add option to configure Ruby's warning behaviour to test runner.
+    Fixes #29717.
     *Yuji Yaginuma*
-*   Initialize git repo when generating new app, if option `--skip-git`
-    is not provided.
-    *Dino Maric*
-*   Install Byebug gem as default in Windows (mingw and x64_mingw) platform.
-    *Junichi Ito*
-*   Make every Rails command work within engines.
-    *Sean Collins*, *Yuji Yaginuma*
-*   Don't generate HTML/ERB templates for scaffold controller with `--api` flag.
-    Fixes #27591.
-    *Prathamesh Sonpatki*
-*   Make `Rails.env` fall back to `development` when `RAILS_ENV` and `RACK_ENV` is an empty string.
-    *Daniel Deng*
-*   Remove deprecated `CONTROLLER` environment variable for `routes` task.
-    *Rafael Mendonça França*
-*   Remove deprecated tasks: `rails:update`, `rails:template`, `rails:template:copy`,
-    `rails:update:configs` and `rails:update:bin`.
-    *Rafael Mendonça França*
-*   Remove deprecated file `rails/rack/debugger`.
-    *Rafael Mendonça França*
-*   Remove deprecated `config.serve_static_files`.
-    *Rafael Mendonça França*
-*   Remove deprecated `config.static_cache_control`.
-    *Rafael Mendonça França*
-*   The `log:clear` task clear all environments log files by default.
+*   Add `rails secrets:show` command.
     *Yuji Yaginuma*
-*   Add Webpack support in new apps via the --webpack option, which will delegate to the rails/webpacker gem.
-    To generate a new app that has Webpack dependencies configured and binstubs for webpack and webpack-watcher:
-      `rails new myapp --webpack`
-    To generate a new app that has Webpack + React configured and an example intalled:
-      `rails new myapp --webpack=react`
-    *DHH*
-*   Add Yarn support in new apps with a yarn binstub and package.json. Skippable via --skip-yarn option.
-    *Liceth Ovalles*, *Guillermo Iguaran*, *DHH*
+*   Allow mounting the same engine several times in different locations.
-*   Removed jquery-rails from default stack, instead rails-ujs that is shipped
-    with Action View is included as default UJS adapter.
+    Fixes #20204.
-    *Guillermo Iguaran*
+    *David Rodríguez*
-*   The config file `secrets.yml` is now loaded in with all keys as symbols.
-    This allows secrets files to contain more complex information without all
-    child keys being strings while parent keys are symbols.
+*   Clear screenshot files in `tmp:clear` task.
-    *Isaac Sloan*
+    *Yuji Yaginuma*
-*   Add `:skip_sprockets` to `Rails::PluginBuilder::PASSTHROUGH_OPTIONS`
+*   Add `railtie.rb` to the plugin generator
     *Tsukuru Tanimichi*
-*   Add `--skip-coffee` option to `rails new`
-    *Seunghwan Oh*
-*   Allow the use of listen's 3.1.x branch
-    *Esteban Santana Santana*
-*   Run `Minitest.after_run` hooks when running `rails test`.
-    *Michael Grosser*
-*   Run `before_configuration` callbacks as soon as application constant
-    inherits from `Rails::Application`.
-    Fixes #19880.
+*   Deprecate `capify!` method in generators and templates.
     *Yuji Yaginuma*
-*   A generated app should not include Uglifier with `--skip-javascript` option.
-    *Ben Pickles*
-*   Set session store to cookie store internally and remove the initializer from
-    the generated app.
-    *Prathamesh Sonpatki*
-*   Set the server host using the `HOST` environment variable.
-    *mahnunchik*
-*   Add public API to register new folders for `rake notes`:
-        config.annotations.register_directories('spec', 'features')
-    *John Meehan*
-*   Display name of the class defining the initializer along with the initializer
-    name in the output of `rails initializers`.
-    Before:
-        disable_dependency_loading
-    After:
-        DemoApp::Application.disable_dependency_loading
-    *ta1kt0me*
+*   Allow irb options to be passed from `rails console` command.
-*   Do not run `bundle install` when generating a new plugin.
+    Fixes #28988.
-    Since bundler 1.12.0, the gemspec is validated so the `bundle install`
-    command will fail just after the gem is created causing confusion to the
-    users. This change was a bug fix to correctly validate gemspecs.
+    *Yuji Yaginuma*
-    *Rafael Mendonça França*
+*   Added a shared section to `config/database.yml` that will be loaded for all environments.
-*   Ensure `/rails/info` routes match in development for apps with a catch-all globbing route.
+    *Pierre Schambacher*
-    *Nicholas Firth-McCoy*
+*   Namespace error pages' CSS selectors to stop the styles from bleeding into other pages
+    when using Turbolinks.
-*   Added a shared section to `config/secrets.yml` that will be loaded for all environments.
+    *Jan Krutisch*
-    *DHH*
-Please check [5-0-stable](https://github.com/rails/rails/blob/5-0-stable/railties/CHANGELOG.md) for previous changes.
+Please check [5-1-stable](https://github.com/rails/rails/blob/5-1-stable/railties/CHANGELOG.md) for previous changes.

data/RDOC_MAIN.rdoc CHANGED

@@ -1,35 +1,50 @@
 == Welcome to \Rails
-\Rails is a web-application framework that includes everything needed to create
-database-backed web applications according to the {Model-View-Controller (MVC)}[http://en.wikipedia.org/wiki/Model-view-controller] pattern.
-Understanding the MVC pattern is key to understanding \Rails. MVC divides your application
-into three layers, each with a specific responsibility.
-The View layer is composed of "templates" that are responsible for providing
-appropriate representations of your application's resources. Templates
-can come in a variety of formats, but most view templates are \HTML with embedded Ruby
-code (.erb files).
-The Model layer represents your domain model (such as Account, Product, Person, Post)
-and encapsulates the business logic that is specific to your application. In \Rails,
-database-backed model classes are derived from ActiveRecord::Base. Active Record allows
-you to present the data from database rows as objects and embellish these data objects
-with business logic methods. Although most \Rails models are backed by a database, models
-can also be ordinary Ruby classes, or Ruby classes that implement a set of interfaces as
-provided by the ActiveModel module. You can read more about Active Record in its
-{README}[link:files/activerecord/README_rdoc.html].
-The Controller layer is responsible for handling incoming HTTP requests and providing a
-suitable response. Usually this means returning \HTML, but \Rails controllers can also
-generate XML, JSON, PDFs, mobile-specific views, and more. Controllers manipulate models
-and render view templates in order to generate the appropriate HTTP response.
-In \Rails, the Controller and View layers are handled together by Action Pack.
-These two layers are bundled in a single package due to their heavy interdependence.
-This is unlike the relationship between Active Record and Action Pack, which are
-independent. Each of these packages can be used independently outside of \Rails. You
-can read more about Action Pack in its {README}[link:files/actionpack/README_rdoc.html].
+\Rails is a web-application framework that includes everything needed to
+create database-backed web applications according to the
+{Model-View-Controller (MVC)}[http://en.wikipedia.org/wiki/Model-view-controller]
+pattern.
+Understanding the MVC pattern is key to understanding \Rails. MVC divides your
+application into three layers, each with a specific responsibility.
+The <em>Model layer</em> represents your domain model (such as Account, Product,
+Person, Post, etc.) and encapsulates the business logic that is specific to
+your application. In \Rails, database-backed model classes are derived from
+ActiveRecord::Base. Active Record allows you to present the data from
+database rows as objects and embellish these data objects with business logic
+methods. You can read more about Active Record in its {README}[link:files/activerecord/README_rdoc.html].
+Although most \Rails models are backed by a database, models can also be ordinary
+Ruby classes, or Ruby classes that implement a set of interfaces as provided by
+the Active Model module. You can read more about Active Model in its {README}[link:files/activemodel/README_rdoc.html].
+The <em>Controller layer</em> is responsible for handling incoming HTTP requests and
+providing a suitable response. Usually this means returning \HTML, but \Rails controllers
+can also generate XML, JSON, PDFs, mobile-specific views, and more. Controllers load and
+manipulate models, and render view templates in order to generate the appropriate HTTP response.
+In \Rails, incoming requests are routed by Action Dispatch to an appropriate controller, and
+controller classes are derived from ActionController::Base. Action Dispatch and Action Controller
+are bundled together in Action Pack. You can read more about Action Pack in its
+{README}[link:files/actionpack/README_rdoc.html].
+The <em>View layer</em> is composed of "templates" that are responsible for providing
+appropriate representations of your application's resources. Templates can
+come in a variety of formats, but most view templates are \HTML with embedded
+Ruby code (ERB files). Views are typically rendered to generate a controller response,
+or to generate the body of an email. In \Rails, View generation is handled by Action View.
+You can read more about Action View in its {README}[link:files/actionview/README_rdoc.html].
+Active Record, Active Model, Action Pack, and Action View can each be used independently outside \Rails.
+In addition to that, \Rails also comes with Action Mailer ({README}[link:files/actionmailer/README_rdoc.html]), a library
+to generate and send emails; Active Job ({README}[link:files/activejob/README_md.html]), a
+framework for declaring jobs and making them run on a variety of queueing
+backends; Action Cable ({README}[link:files/actioncable/README_md.html]), a framework to
+integrate WebSockets with a \Rails application;
+Active Storage ({README}[link:files/activestorage/README_md.html]), a library to attach cloud
+and local files to \Rails applications;
+and Active Support ({README}[link:files/activesupport/README_rdoc.html]), a collection
+of utility classes and standard library extensions that are useful for \Rails,
+and may also be used independently outside \Rails.
 == Getting Started
@@ -45,29 +60,32 @@ can read more about Action Pack in its {README}[link:files/actionpack/README_rdo
 3. Change directory to +myapp+ and start the web server:
-    $ cd myapp; rails server
+    $ cd myapp
+    $ rails server
    Run with <tt>--help</tt> or <tt>-h</tt> for options.
-4. Go to http://localhost:3000 and you'll see:
-    "Yay! You’re on Rails!"
+4. Go to <tt>http://localhost:3000</tt> and you'll see: "Yay! You’re on \Rails!"
 5. Follow the guidelines to start developing your application. You may find the following resources handy:
-* The \README file created within your application.
-* {Getting Started with \Rails}[http://guides.rubyonrails.org/getting_started.html].
-* {Ruby on \Rails Tutorial}[https://www.railstutorial.org/book].
-* {Ruby on \Rails Guides}[http://guides.rubyonrails.org].
-* {The API Documentation}[http://api.rubyonrails.org].
+   * The \README file created within your application.
+   * {Getting Started with \Rails}[http://guides.rubyonrails.org/getting_started.html].
+   * {Ruby on \Rails Guides}[http://guides.rubyonrails.org].
+   * {The API Documentation}[http://api.rubyonrails.org].
+   * {Ruby on \Rails Tutorial}[https://www.railstutorial.org/book].
 == Contributing
-We encourage you to contribute to Ruby on \Rails! Please check out the {Contributing to Rails
-guide}[http://edgeguides.rubyonrails.org/contributing_to_ruby_on_rails.html] for guidelines about how
-to proceed. {Join us}[http://contributors.rubyonrails.org]!
+We encourage you to contribute to Ruby on \Rails! Please check out the
+{Contributing to Ruby on \Rails guide}[http://guides.rubyonrails.org/contributing_to_ruby_on_rails.html] for guidelines about how to proceed. {Join us!}[http://contributors.rubyonrails.org]
+Trying to report a possible security vulnerability in \Rails? Please
+check out our {security policy}[http://rubyonrails.org/security/] for
+guidelines about how to proceed.
+Everyone interacting in \Rails and its sub-projects' codebases, issue trackers, chat rooms, and mailing lists is expected to follow the \Rails {code of conduct}[http://rubyonrails.org/conduct/].
 == License
-Ruby on \Rails is released under the {MIT License}[http://www.opensource.org/licenses/MIT].
+Ruby on \Rails is released under the {MIT License}[https://opensource.org/licenses/MIT].