-
-
Notifications
You must be signed in to change notification settings - Fork 485
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
Context should accept procs as values #963
Comments
If you want to insert some information that's only available after the It could be a bit less convenient than passing a proc value. But since it's achievable, I don't want to support proc value at the moment as the benefit won't worth the added complexity.
We do clean up the context in rack middleware, so you don't need to do it manually |
I used other error tracking libraries and what I'm missing in sentry is the ability to provide context using a proc.
If I provide context in a before action as in the provided example
when filter is run some values may not yet be available. If we're able to provide a proc (evaluated with current controller) we can add more useful data to context and get it when available.
Also I see that you're using thread locals (correctly) but you don't suggest to clear context after usage, this can leak context to other requests served by same thread. I'm using like this to avoid this issue.
is that correct?
The text was updated successfully, but these errors were encountered: