Closed tiagocassio closed 1 year ago
This is good. Thanks!
What's the motivation with using another gem as opposed to ActiveSupport::CurrentAttributes? My understanding of CurrentAttributes
is that it's designed specifically to deal with this problem, and it's already available due to the indirect dependency via ActiveRecord
.
I like the idea of moving to ActiveSupport::CurrentAttributes. I'd love to see a PR with that.
Related to: https://github.com/collectiveidea/audited/issues/601 and inspired by: https://github.com/paper-trail-gem/paper_trail/commit/e28d29ef0f58cded1537df57551b73ac5b081b36