| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
config examples for ActionCable now use Rails.application.config.action_cable
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Some existing examples used ActionCable.server.config but for
configuring allowed_request_origins that is overridden in development
mode. The correct place to set that is
Rails.application.config.action_cable which the ActionCable initializer
loads from. I thought the other two examples should be changed as well
just in case a default value that would override a configured value is
introduced for either log_tags or disable_request_forgery_protection in
the future.
|
|\ \
| | |
| | | |
update turbolinks url [ci skip]
|
|/ / |
|
|\ \
| |/
|/| |
`schema_type` returns symbol rather than string
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
A return value of `schema_type` is used by:
1. primary key type: using as `symbol.inspect`
2. normal column type: using as `symbol.to_s`
It is better to return symbol.
|
|\ \
| | |
| | | |
Added numeric helper into `SchemaStatements` for MySQL and PostgreSQL
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
With this addition, you can add a column into the table like:
```
create_table(:numeric_types) do |t|
t.numeric :foo, precision: 10, scale: 2, default: 2.0
end
```
The result of the migration above is same with:
```
create_table(:numeric_types) do |t|
t.decimal :foo, precision: 10, scale: 2, default: 2.0
end
```
|
|\ \ \
| | | |
| | | | |
doc changes to clarify asset pipeline
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
for rails/rails#23431
modified: guides/source/asset_pipeline.md
* description of asset combination from apps and gems, e.g. jquery-rails
* after @vipulnsward's related change rails/rails#23479
correction: --skip-sprockets will prevent all of these gems, not just sass-rails and uglifier
modified: guides/source/working_with_javascript_in_rails.md
* noted that rails.js requires the asset pipeline
[ci skip]
|
|\ \ \
| | | |
| | | | |
Hand off the interlock to the new thread in AC::Live
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
A full write-preferring wait can lead to deadlock.
|
| | | | |
|
| | |/
| |/|
| | |
| | |
| | |
| | | |
Most importantly, the original request thread must yield its share lock
while waiting for the live thread to commit -- otherwise a request's
base and live threads can deadlock against each other.
|
| | | |
|
|\ \ \
| | | |
| | | | |
Publish guide on "Using Rails for API-only Applications"
|
|/ / /
| | |
| | |
| | |
| | | |
Fixes #23322
[ci skip]
|
| | |
| | |
| | |
| | | |
[ci skip]
|
|\ \ \ |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Follow up of https://github.com/rails/rails/commit/c9feea6c9ab4494b0cb0b8cf4316847854f65af6
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
- Followup of https://github.com/rails/docrails/commit/10bc49710b7205a6172c3e072b3c77114fefd952
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
ActiveRecord's Reflection was refactored by
f8d2899d12d59360f29c5eb6a1b1a8fe4ec82ca0 .
Top of ancestors chain was changed to `AbstractReflection` from
`MacroReflection`, and new Reflections were added.
|
| | | | |
|
|\ \ \ \
| |_|/ /
|/| | | |
fix typo in `assert_enqueued_jobs` example [ci skip]
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
MariaDB does not support JSON type
|
| | | | |
| | | | |
| | | | |
| | | | | |
Fixes #22980.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Referencing Rails.env without checking if it's defined couples
us to Railties.
Fix by avoiding the line breaks if we don't have an env check
to rely on.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Remove unused private method
|
|/ / / / / |
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
Remove duplicated `require 'arel'`
|
| |/ / /
| | | |
| | | |
| | | | |
It appears first in `lib/active_record.rb`.
|
|\ \ \ \
| |/ / /
|/| | | |
Replace old Rails greeting references
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
A couple of the READMEs were still referring the old welcome page. This
is a small change that goes over it.
[ci skip]
|
|\ \ \ \
| | | | |
| | | | | |
Revert "No need to specify Ruby patch version on Travis CI"
|
| | | | | |
|
|\ \ \ \ \
| |_|/ / /
|/| | | | |
Revert "When generating a mailer, you must specify Mailer in the class name in"
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This reverts commit 8417d967e016f0219cc4ec30bf0d3908ce6cd29b.
In 5697bdbb6da5d08e541a3b12251cec90269b059b and af3eb5961e55a46b011be797e71f615f20f56686,
add mailer suffix to generated files and classes.
Therefore, no longer need to specify `Mailer` to class name. [ci skip]
|
| | | | |
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previous commit accidentally broke mixing line filters with string -n filter.
Fix by checking if it is a string and returning it.
We also need to ensure the -n filter carry forward into any other composite filters.
Fix by letting the named filter be extractable, so we'll keep this for the next runnable's
run.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit 99801c6a7b69eb4b006a55de17ada78f3a0fa4c1.
Ultimately it doesn't matter whether `add_index` or `t.index` are used
in the schema dumper in any meaningful way. There are gems out there
which hook into the old behavior for things like indexing materialized
views. Since the reverted commit doesn't seem to add much benefit,
there's no reason for us to break these gems.
|
|\ \ \
| | | |
| | | | |
No need to specify Ruby patch version on Travis CI
|
|/ / /
| | |
| | |
| | |
| | | |
Travis CI now select the latest patch version of Ruby automatically when
given MAJOR.MINOR version string.
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Tests can (and do) access the database from the main thread. In this
case they were starting a transaction, then making a request. The
request would create a new thread, which would allocate a new database
connection. Since the main thread started a transaction that contains
data that the new thread wants to see, the new thread would not see it
due to data visibility from transactions. Spawning the new thread in
production is fine because middleware should not be doing database
manipulation similar to the test harness. Before 603fe20c it was
possible to set the database connection id based on a thread local, but
603fe20c changes the connection lookup code to never look at the
"connection id" but only at the thread object itself. Without that
indirection, we can't force threads to use the same connection pool as
another thread.
Fixes #23483
|
|\ \
| | |
| | | |
When generating a mailer, you must specify Mailer in the class name
|