| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
| |
ref #18961, #23099.
|
|
|
|
|
| |
Related to issue #25581
https://github.com/rails/rails/issues/25581
|
| |
|
|\
| |
| |
| | |
This is an slight refactoring/improved version of #25586.
|
| | |
|
|/
|
|
|
|
|
|
| |
Add following.
* https://github.com/rails/rails/commit/05934d24aff62d66fc62621aa38dae6456e276be
* https://github.com/rails/rails/commit/38d2bf5fd1f3e014f2397898d371c339baa627b1
* https://github.com/rails/rails/pull/25469
|
|\
| |
| | |
Add API Apps to release notes
|
| | |
|
|/
|
|
| |
Make release notes about legacy `mysql` adapter clearer.
|
| |
|
| |
|
|
|
|
|
| |
Fix a tiny typo and vertical-align some return results in the
ActiveModel::Errors documentation.
|
|
|
|
|
|
|
|
|
| |
- https://github.com/rails/rails/pull/18288.
- https://github.com/rails/rails/commit/da9038e.
- https://github.com/rails/rails/commit/78dab2a8569408658542e462a957ea5a35aa4679.
- https://github.com/rails/rails/pull/9065.
- https://github.com/rails/rails/pull/18314.
- https://github.com/rails/rails/pull/13434.
|
|\
| |
| | |
Add missing things to release notes [ci skip]
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- https://github.com/rails/rails/pull/18721
- https://github.com/rails/rails/pull/11898
- https://github.com/rails/rails/pull/18194
- https://github.com/rails/rails/pull/18225
- https://github.com/rails/rails/pull/18244
- https://github.com/rails/rails/commit/edc2b7718725016e988089b5fb6d6fb9d6e16882
- https://github.com/rails/rails/pull/19686
|
|/ |
|
|
|
|
| |
[ci skip]
|
|
|
|
|
| |
`:enum_prefix` and `:enum_suffix` was changed to `:_prefix` and `:_suffix`
in #20999.
|
| |
|
|
|
|
|
|
|
|
| |
Ruby 2.4 unifies Fixnum and Bignum into Integer: https://bugs.ruby-lang.org/issues/12005
* Forward compat with new unified Integer class in Ruby 2.4+.
* Backward compat with separate Fixnum/Bignum in Ruby 2.2 & 2.3.
* Drops needless Fixnum distinction in docs, preferring Integer.
|
|\
| |
| | |
Add Attributes API to release notes [ci skip]
|
| |
| |
| |
| | |
[ci skip]
|
| |
| |
| |
| |
| |
| | |
section of Active Record notes [ci skip]
- Followup of PR #19282.
|
| | |
|
| |
| |
| |
| |
| |
| | |
- Removed duplicate entry for collection caching.
- The entry was duplicate and the link to PR was also wrong.
- Consolidated entries for `belongs_to` required by default.
|
| | |
|
| |
| |
| |
| |
| |
| | |
CHANGELOG and release notes.
[ci skip]
|
| |
| |
| |
| | |
[ci skip]
|
| |
| |
| |
| |
| |
| | |
Fixes #23643.
[ci skip]
|
| |
| |
| |
| | |
[ci skip]
|
|/ |
|
|
|
|
| |
The option backed to `start` in da26934313a31ae530b7537aba8a7662152f4dfe.
|
| |
|
|
|
|
|
|
| |
- Removed entry for # Template Collection from release notes.
- Remove duplicate entry for caching Action mailer views.
- Remove duplicate entry for left_outer_joins.
|
|
|
|
| |
[ci skip]
|
|
|
|
|
|
|
|
| |
[ci skip]
Sync AV, AR, AJ, AS, AM changelogs with our 5.0 release notes draft.
This is a follow up to c94045d and contains changes made since the
release of beta1.
|
|
|
|
|
|
|
|
|
|
| |
[ci skip]
This updates the 5.0 release notes guide to reflect changes that
happened after beta1 has been released.
I'll sync the other changelogs later today but I'll push this batch to
prevent against cumbersome merge conflicts.
|
| |
|
|
|
|
| |
Follow up to ddf4c953ae8d10489e0bfd6008bd76395f6e1267
|
|
|
|
|
| |
* Fixes typos in error message and release notes.
* Removes unused template test file.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. Conceptually revert #20276
The feature was implemented for the `responders` gem. In the end,
they did not need that feature, and have found a better fix (see
plataformatec/responders#131).
`ImplicitRender` is the place where Rails specifies our default
policies for the case where the user did not explicitly tell us
what to render, essentially describing a set of heuristics. If
the gem (or the user) knows exactly what they want, they could
just perform the correct `render` to avoid falling through to
here, as `responders` did (the user called `respond_with`).
Reverting the patch allows us to avoid exploding the complexity
and defining “the fallback for a fallback” policies.
2. `respond_to` and templates are considered exhaustive enumerations
If the user specified a list of formats/variants in a `respond_to`
block, anything that is not explicitly included should result
in an `UnknownFormat` error (which is then caught upstream to
mean “406 Not Acceptable” by default). This is already how it
works before this commit.
Same goes for templates – if the user defined a set of templates
(usually in the file system), that set is now considered exhaustive,
which means that “missing” templates are considered `UnknownFormat`
errors (406).
3. To keep API endpoints simple, the implicit render behavior for
actions with no templates defined at all (regardless of formats,
locales, variants, etc) are defaulted to “204 No Content”. This
is a strictly narrower version of the feature landed in #19036 and
#19377.
4. To avoid confusion when interacting in the browser, these actions
will raise an `UnknownFormat` error for “interactive” requests
instead. (The precise definition of “interactive” requests might
change – the spirit here is to give helpful messages and avoid
confusions.)
Closes #20666, #23062, #23077, #23564
[Godfrey Chan, Jon Moss, Kasper Timm Hansen, Mike Clark, Matthew Draper]
|
| |
|
| |
|
|
|
| |
This is a notable change since this will cause confusing test failures for tests relying on the old naming scheme.
|
| |
|
| |
|
| |
|