| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
Allow static asset serving from env variable (enhanced!)
Conflicts:
railties/CHANGELOG.md
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Closes #17945
`db:test:prepare` still purges the database to always keep the test
database in a consistent state.
This patch introduces new problems with `db:schema:load`. Prior
to the introduction of foreign-keys, we could run this file against
a non-empty database. Since every `create_table` containted the
`force: true` option, this would recreate tables when loading the schema.
However with foreign-keys in place, `force: true` wont work anymore and
the task will crash.
/cc @schneems
|
|\
| |
| | |
Add a code checking about file or not to the rails db command
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
|
|
|
| |
See 63462ec
|
| |
|
|\
| |
| | |
fixing mailer previews for apps with globbing route
|
| | |
|
|\ \
| | |
| | | |
Test coverage for ActiveJob generator
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes:
http://intertwingly.net/projects/AWDwR4/checkdepot-215/makedepot.log
|
|\ \ \
| | | |
| | | | |
Don't remove mailer layouts files
|
| | | | |
|
| |_|/
|/| | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Without this,
% rails r "require 'rails/tasks'"
would cause a NoMethodError: undefined method `desc' for main:Object
|
| |/
|/|
| |
| |
| |
| |
| |
| | |
Fixes https://github.com/rails/rails/issues/17340.
Use Minitest::BacktraceFilter instead of removing all silencers. This
will allow the backtrace for all libraries in the plugin to be shown
while removing noise generated by Minitest's backtrace.
|
|\ \
| | |
| | | |
Bugfix config.action_view.default_form_builder option
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
Pure rack apps can be mounted with a name
|
| |/ /
| | |
| | |
| | | |
See https://github.com/rails/rails/commit/9b15828b5c347395b42066a588c88e5eb4e72279#commitcomment-8764492
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
[This article](http://weblog.rubyonrails.org/2014/8/20/Rails-4-2-beta1/#maintenance-consequences-and-rails-5-0) states that:
> Rails 5.0 is in most likelihood going to target Ruby 2.2.
Before the exact minimum version is fully decided, @arthurnn [suggests](https://github.com/rails/rails/pull/17830#issuecomment-64940383)
that **at least** version 2.1.0 **must** be required by the `gemspec` files.
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| | |
Change originated from https://github.com/rails/rails/pull/17739#issuecomment-64829088
/cc @metaskills
|
| |
| |
| |
| | |
This reverts commit 2a4e14db981e38611667d407a975600ee720ada7.
|
|/ |
|
| |
|
|\
| |
| |
| | |
be more general with adapter name
|
| | |
|
|\ \
| | |
| | | |
Use absolute_path of caller_locations to infer engine root
|
| | |
| | |
| | |
| | |
| | | |
According to documentation `path` only returns file names. On MRI it's
not the case but it's likely a bug in MRI.
|
|/ / |
|
| | |
|
|\ \
| | |
| | | |
Use web_console 2.0 for 4.2.0.rc1 release
|
| | |
| | |
| | |
| | |
| | | |
This one replaces the notable web-console mentions in guide and the
default Gemfile.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
|/ / |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts deprecations added in #13528.
The task is brought back for two reasons:
1. Give plugins a way to hook into the test database initialization process
2. Give the user a way to force a test database synchronization
While `test:prepare` is still a dependency of every test task, `db:test:prepare`
no longer hooks into it. This means that `test:prepare` runs before the schema
is synchronized. Plugins, which insert data can now hook into `db:test:prepare`.
The automatic schema maintenance can't detect when a migration is rolled-back,
modified and reapplied. In this case the user has to fall back to `db:test:prepare`
to force the synchronization to happen.
|
| |
| |
| |
| |
| |
| | |
The tests to verify our testing setup used `RAILS_ENV=development`
to execute the tests. Let's keep it as close to a real-world setup
as possible.
|
| |
| |
| |
| |
| |
| | |
Closes #17756
[Godfrey Chan, Zachary Scott]
|