- Default to Rails::DeprecatedSanitizer in ActionView::Helpers::SanitizeHelper.
- Add upgrade notes.
- Add sanitizer to new applications Gemfiles.
- Remove 'rails-dom-testing' as a dependency.
The previous code example for the new explicit block requirement when
setting callbacks was a little confusing. This commit makes the example
more obvious.
It is now expected in 4.1 to use an explicit block rather than implicit
when setting callbacks through ActiveSupport::Callbacks. This commit
highlights this new expectation as part of the upgrading documentation.
Point to future 4-2-stable branch for detailed changes. [ci skip]
Sync Active Support changelogs with release notes [ci skip]
4.2 Release Notes is a work in progress [ci skip]
Assorted fixes for AS release notes [ci skip]
* `Hash#deep_transform_keys` has already been backported
* Mentioning `ActiveSupport::SafeBuffer#prepend` in the "Deprecations" section would be enough
* Fix syntax in `Kernel#concern` example
Sync AS release notes with the latest commits [ci skip]
Synced 4.2 release notes with commits in railties [ci skip]
Sync AP Deprecations and Notable changes from CHANGELOG [ci skip]
Removed 4.2 release notes from the index [ci skip]
This deprecation was reverted in 489a8f2 [ci skip]
Synced Active Record changelogs for 4.2 release notes [ci skip]
Synced Active Model changelog with the release notes [ci skip]
Added cc26b6b as a 'Removal' item in AP release notes [ci skip]
Use 'character' instead of 'symbol' to avoid confusion [ci skip]
Edit pass on 4.2 release notes [ci skip]
📝💄 Use `.xyz` and `#xyz` appropiately [ci skip]
* Move check from generated helper to test_help.rb, so that all
applications can benefit
* Rather than just raising when the test schema has pending migrations,
try to load in the schema and only raise if there are pending
migrations afterwards
* Opt out of the check by setting
config.active_record.maintain_test_schema = false
* Deprecate db:test:* tasks. The test helper is now fully responsible
for maintaining the test schema, so we don't need rake tasks for this.
This is also a speed improvement since we're no longer reloading the
test database on every call to "rake test".
