-
Notifications
You must be signed in to change notification settings - Fork 58
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
Update email_account
resource to connected_account
#63
Comments
email_account
resource to connected_account
email_account
resource to connected_account
@AlecRosenbaum Is the response structure the same? |
@taylorbrooks Yes, you get exactly the same fields you would get from |
@taylorbrooks We'd really appreciate any help you can give us to push this forward. |
@neob91-close I'm happy to accept PRs! |
Opened a PR: #83. I have 0 experience with Ruby though, so I could really use your help in making sure that the change works okay. |
Hi!
I noticed that this gem has a resource for accessing
email_account
on the api, and I can also see some traffic on that endpoint from this gem. Would it be possible to update or replace the resource to hitconnected_account
instead?I'm not sure if
email_account
was documented at one point, but internally we've been moving away from it in favor ofconnected_account
for some time now. The connected account endpoint should be better documented, and will be better supported going forward!I'm not very experienced with ruby, but if it's as simple as
s/email/connected/g
within the ruby code I can submit a patch.The text was updated successfully, but these errors were encountered: