| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
[Carlos Antonio da Silva & Santiago Pastorino]
|
|
|
|
| |
[Carlos Antonio da Silva & Santiago Pastorino]
|
|
|
|
| |
[Carlos Antonio da Silva & Santiago Pastorino]
|
|
|
|
|
|
|
| |
Change application controller template accordingly, to inherit from
ActionController::HTTP and not generate protect_from_forgery call.
[Carlos Antonio da Silva & Santiago Pastorino]
|
|
|
|
|
|
| |
More info http://edgeguides.rubyonrails.org/api_app.html
[Carlos Antonio da Silva & Santiago Pastorino]
|
|
|
|
| |
the 1.9 hash syntax in the generators.
|
|
|
|
| |
sprockets-rails release on rubygems
|
| |
|
|\
| |
| | |
Refactor the test_unit scaffold generator to use the key_value method
|
| | |
|
|\ \
| | |
| | | |
Remove Active Resource source files from the repository.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Dear Active Resource,
It's not that I hate you or anything, but you didn't get much attention lately. There're so many alternatives out there, and I think people have made their choice to use them than you. I think it's time for you to have a big rest, peacefully in this Git repository.
I will miss you,
@sikachu.
|
|/ / |
|
|\ \
| |/
|/| |
|
| | |
|
|\ \
| | |
| | | |
Do not use the attributes hash in the scaffold functional tests
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
when ActiveRecord is according to test_help.rb).
|
| | | |
|
|/ /
| |
| |
| | |
production so that PID and timestamp are logged. fixes #5388
|
|\ \
| |/
|/| |
configure how unverified request will be handled
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
can be configured using `:with` option in `protect_from_forgery` method
or `request_forgery_protection_method` config option
possible values:
- :reset_session (default)
- :exception
new applications are generated with:
protect_from_forgery :with => :exception
|
|/
|
|
|
|
|
| |
Reason: Temporarily reverting this because it has uncovered an issue that
prevents Sam's test suite from passing.
This reverts commit 9b2c38b7bd582d9712c3779294a9bccde7bbd548.
|
| |
|
|
|
|
| |
Change the default for newly generated applications to whitelist all attribute assignment. Also update the generated model classes so users are reminded of the importance of attr_accessible.
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|