-
Notifications
You must be signed in to change notification settings - Fork 4
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
Option to use a different ActiveRecord class than RestClient #7
Comments
Would you be interested in submitting a patch for this? |
I don't mind giving a try. It might not be for a little while because I'm pushing hard on a project for the next month or two. |
I really like this Gem and use it in my Konugo server. I am looking into a quick change for this because I ran into a conflict. |
* Closed Issue davesloan#7 - Option to use a different ActiveRecord class than RestClient * This update involves a lot of changes to a lot of files, but the functionality remains the same. The change was to rename RestClient to RestAppClient and rest_client to rest_client. This avoids a conflict with the popular rest-client gem that uses the same RestClient class name.
This change really should be merged in - I understand the issue of backwards compatibility, but can you not make the class configurable and default it to the original? |
Thanks for this library, it is a really simple solution to a problem that I seem to encounter a lot. One suggestion I'd like to make is to allow a developer to name their ActiveRecord class something other than "RestClient".
The text was updated successfully, but these errors were encountered: