| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
as it is
Since #35709, `Response#conten_type` returns only MIME type correctly.
It is a documented behavior that this method only returns MIME type, so
this change seems appropriate.
https://github.com/rails/rails/blob/39de7fac0507070e3c5f8b33fbad6fced84d97ed/actionpack/lib/action_dispatch/http/response.rb#L245-L249
But unfortunately, some users expect this method to return all
Content-Type that does not contain charset. This seems to be breaking
changes.
We can change this behavior with the deprecate cycle.
But, in that case, a method needs that include Content-Type with
additional parameters. And that method name is probably the
`content_type` seems to properly.
So I changed the new behavior to more appropriate `media_type` method.
And `Response#content_type` changed (as the method name) to return Content-Type
header as it is.
Fixes #35709.
[Rafael Mendonça França & Yuuji Yaginuma ]
|
|\ \
| | |
| | | |
Add a section to introduce pluck's eager loading behavior [ci skip]
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | | |
[documentation][ci skip] stringify_keys and symbolize_keys have stable results.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Rails 6 uses the `Hash.transform_keys` found in Ruby 2.5 and later, and that method enumerates keys based on insertion order. Calling `symbolize_keys`, `stringify_keys`, and their bang variants will result in the same hash every time -- the value for any key where a collision occurs is the last assigned in that enumeration
In the docs for Hash -- https://ruby-doc.org/core-2.5.0/Hash.html
> Hashes enumerate their values in the order that the corresponding keys were inserted.
|
|/ / /
| | |
| | |
| | |
| | | |
'Week day' has a specific meaning in English -- see https://en.wiktionary.org/wiki/weekday for details -- that is not meant here. 'Day of week' is more appropriate.
[ci skip]
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
[ci skip] (#36326)
- This hook was added in 90296674b1c
|
|\ \ \
| | | |
| | | | |
List available skip options in command line guide
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
[skip ci] Add undefined STI acronym to the heading which is referred under its section
|
| | | | |
| | | | |
| | | | |
| | | | | |
its section
|
| |/ / /
|/| | |
| | | |
| | | | |
In Adding More RESTful Actions, Adding Member Routes:
I believe the word 'that' should be added to the sentence, 'Within the block of member routes, each route name specifies the HTTP verb will be recognized.' This results in 'Within the block of member routes, each route name specifies the HTTP verb that will be recognized.'
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
soartec-lab/update_guide_configuring_add_autoloader
Added guide for `config.autoloader` [skip ci]
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
To avoid word wrap in the rendered guide.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
config.active_record.collection_cache_versioning without loading Railtie is false
Please check https://github.com/rails/rails/pull/36260#discussion_r283266942 for reference.
[Vishal Telangre, bogdanvlviv]
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
vishaltelangre/active_record-collection_cache_versioning-config-info
[skip ci] Add missing info about 'active_record.collection_cache_versioning' configuration
|
| | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
configuration
References:
- https://github.com/rails/rails/commit/4f2ac80d4cdb01c4d3c1765637bed76cc91c1e35
- https://github.com/rails/rails/blob/b1c917ee2fdaa452aeb52904db0d254d85285380/railties/lib/rails/application/configuration.rb#L147-L149
|
|\ \ \ \ \
| | | | | |
| | | | | | |
[ci skip] Clarity about embed metadata in signed and encrypted cookie
|
| | | | | | |
|
| | | | | | |
|
| |/ / / /
|/| | | |
| | | | |
| | | | | |
According to https://www.npmjs.com/.
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
compilation -> compression [ci skip]
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
[ci skip] Clarify that the minimum version of a "gem" is bumped
|
| | |/ / / /
| |/| | | |
| | | | | |
| | | | | | |
The previous sentence does not convey whether the minimum version of SQLite3 is bumped or the minimum version of `sqlite3` gem is bumped.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
[ci skip] Typo: Javascript -> JavaScript
|
| |/ / / / / |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
[ci skip] Fix grammar
|
| |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
##### Singular
`route exists`
##### Plural
`routes exist`
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
[ci skip] mysql -> MySQL
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
[ci skip] ActionView -> Action View
|
| | |/ / / / /
| |/| | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
As per the documentation guides, we use 'Action View' instead of `ActionView` in the general language.
Reference: https://github.com/rails/rails/commit/27138386ad8dbda2eb44e622515626f352fd3b22
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
[ci skip] Mime -> MIME
|
| |/ / / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The correct word is `MIME` which is an acronym which stands for `Multipurpose Internet Mail Extensions`.
Reference: https://en.wikipedia.org/wiki/MIME
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
[ci skip] Expand JS to JavaScript for clarity
|
| |/ / / / / / |
|
|\ \ \ \ \ \ \
| |_|/ / / / /
|/| | | | | | |
[skip ci] arel -> Arel
|
| |/ / / / /
| | | | | |
| | | | | | |
As per the documentation guides, we write `Arel` instead of `arel`.
|
|/ / / / / |
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
vishaltelangre/fix-confusing-sentence-in-upgrade-guide
[ci skip] Fix confusing sentence in upgrade guide
|
| | | | | | |
|
|/ / / / / |
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
Closes #28707.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Fixes GH#28706. Now rails g migration create_users and rails g model User have the same behavior for timestamps since they implement the same migration template. The expected behavior is that this create table migration will create the table with timestamps unless you pass --no-timestamps or --skip-timestamps to the generator. The expected migration should match what you get when you use the model generator. Using the migration generator, which doesn't have a class_option for timestamps would cause them to not be added to the migration file. Now the migration behavior of the migration generator, create_table only, is aligned with the migration behavior of the model generator. Also modified relevant example of ActiveRecord Migrations Guide.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Introduce ActiveSupport::Notifications.monotonic_subscribe
|