-
Notifications
You must be signed in to change notification settings - Fork 72
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
Resource instances don't hit API? #96
Comments
Hi @excid3 Thanks for spotting and reporting the problem. We will investigate further on our end. In the meantime, we will be more than happy to review your contribution |
Fantastic, thanks guys! Will update to that and let you know if I run into any issues. |
Awesome, thanks @excid3 for your feedback and time. Looking forward to hear back! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Was doing some debugging today and noticed that resource instance methods like
update_attributes
don't hit the API. Since instance methods don't call thechange_resource_path
like the class methods do, they don't get the correct endpoint, version, and so on.Should these methods be updated in
Resource
to call that? For example, modifying the method like this works:The text was updated successfully, but these errors were encountered: