Does Rails (5.2+) ActiveSupport::CurrentAttributes have same functionality as this gem?

[eoinkelly]

It seems like Rails' built-in (since 5.2) ActiveSupport::CurrentAttributes has the same functionality as this gem.

If my reading is correct then I think we should add a note to the README explaining this and perhaps encouraging using that instead. If I'm wrong then a note explaining the difference would be equally useful.

[steveklabnik]

I haven't used Rails since Rails 4, if anyone knows this answer, I would be happy to take a PR explaining it.

[alexeyr-ci]

E.g. I use RequestStore to make sure a <script> tag only gets inserted once even if a partial which includes it is rendered several times. It very much doesn't fall under

The attributes stuck in Current should be used by more or less all actions on all requests. If you start sticking controller-specific attributes in there, you're going to create a mess.

[brendon]

It was easy enough to do with something like:

class Current < ActiveSupport::CurrentAttributes
  attribute :something
end

Current.something ||= begin
  'cached value'
end

or if you declare your current attribute with a default of {} you can do:

class Current < ActiveSupport::CurrentAttributes
  attribute :can, default: {}
end

Current.can[variable_value] ||= begin
  'cached value'
end