Update deprecation tracker to support newer Rails versions (7.1+) #142
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Since Rails 7.1 the preferred way to track deprecations is to access the deprecation trackers via
Rails.application.deprecators
.Here, we change the implementation to use that if it is available, otherwise fallback to tracking deprecations via the
ActiveSupport::Deprecation
singleton object for older Rails versions.Related Rails changes:
Motivation and Context
This is required to avoid getting deprecation warnings when using
next_rails
on Rails 7.1+ versions.Additionally, eventually access via the singleton will be retired, this change will ensure we can still track deprecations when that happens.
How Has This Been Tested?
I added new specs to test this functionality.
Additionally, I tested this against a Rails 7.1 project and check that we received the expected deprecation warnings.
Screenshots:
n/a
I will abide by the code of conduct ✅