Fixup CHANGELOGs [ci skip]

This commit is contained in:
Ryuta Kamizono 2020-04-15 21:23:24 +09:00
parent 943f1ea1ea
commit 6f2126c760
5 changed files with 33 additions and 31 deletions

View File

@ -16,6 +16,8 @@
end
```
*Étienne Barrié*
* `ActiveJob::TestCase#perform_enqueued_jobs` will no longer perform retries:
When calling `perform_enqueued_jobs` without a block, the adapter will
@ -26,7 +28,7 @@
*Edouard Chin*
* Add queue name support to Que adapter
* Add queue name support to Que adapter.
*Brad Nauta*, *Wojciech Wnętrzak*
@ -40,7 +42,7 @@
`after_enqueue` and `after_perform` callbacks will no longer run if the callback chain is halted.
This behaviour is a breaking change and won't take effect until Rails 6.2.
To enable this behaviour in your app right now, you can add in your app's configuration file
`config.active_job.skip_after_callbacks_if_terminated = true`
`config.active_job.skip_after_callbacks_if_terminated = true`.
*Edouard Chin*

View File

@ -29,14 +29,14 @@
* Encapsulate each validation error as an Error object.
The `ActiveModel`s `errors` collection is now an array of these Error
The `ActiveModel`s `errors` collection is now an array of these Error
objects, instead of messages/details hash.
For each of these `Error` object, its `message` and `full_message` methods
are for generating error messages. Its `details` method would return errors
For each of these `Error` object, its `message` and `full_message` methods
are for generating error messages. Its `details` method would return errors
extra parameters, found in the original `details` hash.
The change tries its best at maintaining backward compatibility, however
The change tries its best at maintaining backward compatibility, however
some edge cases wont be covered, like `errors#first` will return `ActiveModel::Error` and manipulating
`errors.messages` and `errors.details` hashes directly will have no effect. Moving forward,
please convert those direct manipulations to use provided API methods instead.
@ -55,4 +55,5 @@
*lulalala*
Please check [6-0-stable](https://github.com/rails/rails/blob/6-0-stable/activemodel/CHANGELOG.md) for previous changes.

View File

@ -4,7 +4,7 @@
* Prevent `build_association` from `touching` a parent record if the record isn't persisted for `has_one` associations.
Fixes #38219
Fixes #38219.
*Josh Brody*
@ -15,11 +15,11 @@
Usage:
```
```ruby
add_index :users, :account_id, if_not_exists: true
```
The `if_not_exists` option passed to `create_table` also gets propogated to indexes
The `if_not_exists` option passed to `create_table` also gets propagated to indexes
created within that migration so that if table and its indexes exist then there is no
attempt to create them again.
@ -29,7 +29,7 @@
*Tom Ward*
* Support descending order for `find_each`, `find_in_batches` and `in_batches`.
* Support descending order for `find_each`, `find_in_batches`, and `in_batches`.
Batch processing methods allow you to work with the records in batches, greatly reducing memory consumption, but records are always batched from oldest id to newest.
@ -45,7 +45,7 @@
*Alexey Vasiliev*
* Fix insert_all with enum values
* Fix `insert_all` with enum values.
Fixes #38716.
@ -61,7 +61,7 @@
*Eugene Kenny*
* Deprecate using `return`, `break` or `throw` to exit a transaction block
* Deprecate using `return`, `break` or `throw` to exit a transaction block.
*Dylan Thacker-Smith*
@ -192,14 +192,14 @@
Usage:
```
>> class Developer < ApplicationRecord
>> has_many :projects, strict_loading: true
>> end
>>
>> dev = Developer.first
>> dev.projects.first
=> ActiveRecord::StrictLoadingViolationError: The projects association is marked as strict_loading and cannot be lazily loaded.
```ruby
class Developer < ApplicationRecord
has_many :projects, strict_loading: true
end
dev = Developer.first
dev.projects.first
# => ActiveRecord::StrictLoadingViolationError: The projects association is marked as strict_loading and cannot be lazily loaded.
```
*Kevin Deisz*
@ -210,10 +210,10 @@
Usage:
```
>> dev = Developer.strict_loading.first
>> dev.audit_logs.to_a
=> ActiveRecord::StrictLoadingViolationError: Developer is marked as strict_loading and AuditLog cannot be lazily loaded.
```ruby
dev = Developer.strict_loading.first
dev.audit_logs.to_a
# => ActiveRecord::StrictLoadingViolationError: Developer is marked as strict_loading and AuditLog cannot be lazily loaded.
```
*Eileen M. Uchitelle*, *Aaron Patterson*
@ -312,7 +312,7 @@
*Eileen M. Uchitelle*
* Deprecate "primary" as the connection_specification_name for ActiveRecord::Base.
* Deprecate `"primary"` as the `connection_specification_name` for `ActiveRecord::Base`.
`"primary"` has been deprecated as the `connection_specification_name` for `ActiveRecord::Base` in favor of using `"ActiveRecord::Base"`. This change affects calls to `ActiveRecord::Base.connection_handler.retrieve_connection` and `ActiveRecord::Base.connection_handler.remove_connection`. If you're calling these methods with `"primary"`, please switch to `"ActiveRecord::Base"`.
@ -531,7 +531,7 @@
*Josh Goodall*
* Add database_exists? method to connection adapters to check if a database exists.
* Add `database_exists?` method to connection adapters to check if a database exists.
*Guilherme Mansur*

View File

@ -1,7 +1,7 @@
* Add support for creating variants of `WebP` images out of the box.
*Dino Maric*
* Only enqueue analysis jobs for blobs with non-null analyzer classes.
*Gannon McGibbon*

View File

@ -18,7 +18,6 @@
Time.at(1498099140 + Rational("1/3")).in_time_zone.inspect
# => "Thu, 22 Jun 2017 02:39:00.333333333 UTC +00:00"
*akinomaeni*
* Calling `ActiveSupport::TaggedLogging#tagged` without a block now returns a tagged logger.
@ -32,10 +31,10 @@
* Align `Range#cover?` extension behavior with Ruby behavior for backwards ranges.
`(1..10).cover?(5..3)` now returns `false`, as it does in plain Ruby.
Also update `#include?` and `#===` behavior to match.
*Michael Groeneman*
*Michael Groeneman*
* Update to TZInfo v2.0.0.
@ -48,7 +47,7 @@
See the `utc_to_local_returns_utc_offset_times` documentation for details.
*Phil Ross and Jared Beck*
*Phil Ross*, *Jared Beck*
* Add Date and Time `#yesterday?` and `#tomorrow?` alongside `#today?`.