| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
| |
The majority of Rails applications are multiprocess, people
may wonder why rails new generates a default pool of 5, does
my application need a connection pool of 5? By generating
a default of 1 database.yml is much more clear, and with
the comment people know what is the connection pool for,
and they know it has to be bigger for multithread apps.
|
|
|
|
|
|
| |
There was a mix, sometimes patch first, sometimes put first.
Use always patch first, since this is going to be the
primary verb for updates.
|
|
|
|
| |
the update action of resources
|
|
|
|
|
|
|
|
|
|
| |
The reconnect flag does not play nicely with transactions and so
it is of little use in Rails applications. Thus, albeit supported
by mysql2, it does not deserve such a prominent place in the
generated database.yml, which should be a representative config
example. Note that the flag is false by default.
Advanced users know from mysql2 docs that the flag is available.
|
|
|
|
| |
MySQL
|
| |
|
|
|
|
|
|
| |
This accidentally ended up in the development template
instead of the production template, where it makes
most sense.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
PATCH is the correct HTML verb to map to the #update action. The
semantics for PATCH allows for partial updates, whereas PUT requires a
complete replacement.
Changes:
* adds config.default_method_for_update you can set to :patch
* optionally use PATCH instead of PUT in resource routes and forms
* adds the #patch verb to routes to detect PATCH requests
* adds #patch? to Request
* changes documentation and comments to indicate support for PATCH
This change maintains complete backwards compatibility by keeping :put
as the default for config.default_method_for_update.
|
|
|
|
|
|
| |
It is usually useful to be able to hide a generator when running rails
generate command. Such generators might be used only to dry up
generators code and shouldn't be available to end users.
|
|
|
|
| |
See https://github.com/rails/rails/pull/4684#commitcomment-920313
|
|\
| |
| | |
Fix broken test introduced from #4814
|
| |
| |
| |
| |
| |
| | |
* ruby_debugger_gemfile_entry was removed from the generator. Please
make sure to run `grep` or `ack` to make sure it was removed in every
places.
|
|/ |
|
|
|
|
| |
ruby-debug19 commented directly in Gemfile
|
| |
|
| |
|
|\
| |
| | |
has_many/has_one, :dependent => :restrict, deprecation added
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Character classes are the specific regexp construct
to express alternation of individual characters.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
As explained in #4764, when destroying a scaffold, routes.rb loses a
new line. This seems to happen because a new line is added
while generating the route and the destroy generator removes it.
However, this causes a problem if the routes file is manually edited
to remove such new lines. This commit just removes that extra new line
from added in the first place.
|
|/ |
|
|
|
|
|
| |
This reverts commit eafa1c429835e099897a0da90bc39d9dbbb7ed4e, reversing
changes made to f251437415f7b803f7a84118fcc970a111ace266.
|
| |
|
|\
| |
| | |
Use `:rubygems` shortcut as standard Gemfile's `source` instead of explicit URL
|
| |
| |
| |
| |
| |
| | |
URL.
Theoretically this would future-proof Gemfiles against possible (albeit unlikely) change in the rubygems URL.
|
|/ |
|
| |
|
|
|
|
|
|
|
|
| |
bash, zsh, etc, closes #4602
Conflicts:
railties/test/generators/migration_generator_test.rb
|
|
|
|
|
|
| |
Some end with a full stop, some don't. Let's have attention to detail
and make them uniform. I have chosen to add full stops according to
our documentation guidelines related to RDoc.
|
|
|
|
|
| |
it's needed until new rack release with Rack::BodyProxy fixes
https://github.com/rack/rack/commit/b06ef82876416fe69429f7d3ee6e51bf26aec75f
|
|
|
|
|
|
| |
The commit 2f632f53919d2b44dbb2cfaadabed2310319f005 extracted the
options into constants and while doing so, there was a minor error of
using a wrong constant name.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
After vendor/plugins were removed from rails, the new method to create
plugins is to create gem plugins. Most of the time if you create a
new plugin in rails application's directory, you want to extract
something from that application and use it immediately, ie. add
such line to Gemfile:
gem 'foo', :path => './vendor/foo'
This commit makes plugin new generator to add such line automatically.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Rails template creation issue
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
particular property should be an index like this 'rails g model person name:string:index profile:string'
|