-
Notifications
You must be signed in to change notification settings - Fork 3
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
UID returns client access_token instead of user id? #4
Comments
This was causing a problem in my app because the I made this change in my local gem, and it works as expected. I'd like to submit a PR, however I'm not sure how to write a test for this. Do you have any thoughts on that? |
A PR would be welcome! This gem was originally authored by an external party, which is probably how this slipped through. You could look to the way the GitHub omniauth gem stubs out |
Good deal... I've got that PR ready for you |
Currently the
uid
attribute returns the access_token for the client request:It seems like the
uid
attribute should return the Drip user's ID instead:The text was updated successfully, but these errors were encountered: