Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Requested Talk: How do CurrentAttributes work? #242

Open
HashNotAdam opened this issue Sep 20, 2024 · 1 comment
Open

Requested Talk: How do CurrentAttributes work? #242

HashNotAdam opened this issue Sep 20, 2024 · 1 comment
Assignees
Milestone

Comments

@HashNotAdam
Copy link
Collaborator

Description:
Rails includes a class called ActiveSupport::CurrentAttributes that can be used to store values that relate only to the current request or job.

For example:

class Current < ActiveSupport::CurrentAttributes
  attribute :user
end

Current.user = User.first

How does Rails store these values?
How can it ensure these values can only be read in the current request?
What happens when you change the isolation level?
From a practical standpoint, what does the isolation level mean?

Estimated Talk Time:
10–15 minutes

@darkfishy
Copy link

@HashNotAdam and @simran-sawhney
I could talk about this in November, with proper presentation slides then 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants