After c2fe0938, which was reverted yesterday, there will likely be
future PRs to address #17661.

The test `actionview/test/template/capture_helper_test.rb
#test_capture_returns_nil_if_the_returned_value_is_not_a_string` should
have errored with c2fe0938, but it was rewritten in the PR to not raise.
My guess is that it may have seemed irrelevant to the content_tag tests
or already covered by them.

This test provides additional protection by being in the content_tag
test suite to explicitly raise a red flag in future cases. It foregoes
some redundancy for safety — at least until #17661 is closed.

Improve section in constant autoload guide

Remove misleading test: around_action return false

English fix [ci skip]

Improve grammar

[skip ci]

Constant autoload grammar fix

[skip ci]

[skip ci]

[ci skip] ✂ blank lines between list items.

[ci skip]

/cc @sgrif @zzak

Conflicts:
	activerecord/CHANGELOG.md

I think "What" is was fine, "The purpose of" assumes the reader knows such thing exists.
"What is" is fine, and also matches the following "What is require_dependency".

4.2.0", then they should have no problems hacking with Rails. [ci skip]

If they do, then its a bug and it should be reported.

Improving tips about installation in the guides [ci skip]

[ci skip]

Conflicts:
	guides/source/constant_autoloading_and_reloading.md

Counter cache Rails guides fix

Adding method chaining section on ActiveRecord querying guide [ci skip]

[ci skip]

Improve autoload_paths section [ci skip]

You need to specify the counter_cache option on the has_many side of the association when using a custom counter cache column. This is documented on the has_many association here: http://apidock.com/rails/ActiveRecord/Associations/ClassMethods/has_many [ci skip]

When an `around_action` does not `yield`, then the corresponding action is
*never* executed and the `after_` actions are *never* invoked.

The value returned by the `around_action` does not have any impact on this:
an `around_action` can "return" `true`, `false`, or `"pizza"`, but as long
as `yield` is not invoked, the corresponding action and after callbacks are
not executed.

The test suite for `ActionController::Callbacks` currently includes separate
tests to distinguish the cases in which a non-yielding `around_actions` returns
`true` or `false`.

In my opinion, having such tests is misleading, giving the impression that the
returned value might have some sort of impact, while it does not. At least
that's the impression I got when I read those tests.

For completeness, the tests were introduced 7 years ago by @NZKoz in e80fabbb.

Minor typos/fixes to autoloading guide

@fxn Great job with the guide, I read it all! Yeah!

Some paragraphs might be restructured, but I'll leave that to you
since you are currently working on it. This commit only includes
some minor typos and commas that in my opinion clarify the reading.

[ci skip]

This reverts commit c2fe0938.

Don't convert empty arrays to nils when deep munging params

Dynamic finders already deprecated [ci skip]

[skip ci]

Follow-up to previous commit

[skip ci]

Fix previous merge

[skip ci]

[skip ci]

fix a typo [ci skip]