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

detect private current_* methods #31

Merged
merged 1 commit into from
Jul 28, 2022
Merged

Conversation

misaka
Copy link
Contributor

@misaka misaka commented Jul 27, 2022

Some services may declare current_user (or current_* really) as private methods if there is no need to expose that method in the controller. Previously we would miss out on sending the user_id with the event if this was the case, this change allows us to detect these as private methods.

For testing purposes, we've made the current_* methods private since that ensures we work with both private and public versions of these methods.

Some services may declare current_user (or current_* really) as private
methods if there is no need to expose that method in the controller.
Previously we would miss out on sending the user_id with the event if
this was the case, this change allows us to detect these as private
methods.

For testing purposes, we've made the current_* methods private since
that ensures we work with both private and public versions of these
methods.
@misaka misaka force-pushed the allow-private-current-user branch from bc550ae to a2b5462 Compare July 27, 2022 13:58
@misaka misaka merged commit 58b0d41 into main Jul 28, 2022
@misaka misaka deleted the allow-private-current-user branch July 28, 2022 09:13
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

Successfully merging this pull request may close these issues.

2 participants