We'll likely need to swap activemodel-caution over to the new structure, as well as mirror the deprecations.
Frustratingly, we've still got a number of use cases for the "active" warnings... regardless, I wonder if it might not be possible to change how this gem functions - to give objects a proxy "warning object" that uses ActiveModel::Error, meaning we'd not be duplicating the entire library.
Rails 6.1 has changed how errors are structured internally, which will affect how
activemodel-caution
should function.See the new API docs.
We'll likely need to swap
activemodel-caution
over to the new structure, as well as mirror the deprecations.Frustratingly, we've still got a number of use cases for the "active" warnings... regardless, I wonder if it might not be possible to change how this gem functions - to give objects a proxy "warning object" that uses
ActiveModel::Error
, meaning we'd not be duplicating the entire library.