-
Notifications
You must be signed in to change notification settings - Fork 982
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
Forward env to Authorization#header_from ? #1449
Comments
Oh, this would then be used in the authorization value proc, I see! Quick early feedback: I think testing |
Cool! I'll start working on it for real then. Thing is, I don't think anything will prevent a user from passing a lambda in, and it will return true for .is_a?(Proc). I appreciate the feedback, I'm pretty unhappy with how that looks ATM even though I left deliberately left it ugly for the diff to be smaller. |
Good shout, I always forget about that! |
Thank you so much! Closing now, PR as I'm able |
Basic Info
Would a PR that forwards env to Authorization#header_from be considered? If no, I can understand wanting to limit complexity. But something along these lines (simplified to minimize the diff):
Specs and passing rubocop would accompany a real PR if something along these lines would be considered. Where would be the best place to update documentation?
Thanks!
The text was updated successfully, but these errors were encountered: