Allow calls to instantiate_record in ActiveResource for Custom Actions
Reported by Matthew Moore | June 6th, 2008 @ 12:48 AM
Right now, to consume custom actions, you have to call .get(:custom_action). This returns a hash, as opposed to a record like .find does.
For my purposes, I need to instantiate the resulting hash into a record. However, there's no way for me to do that because instantiate_record is private. Same goes for instantiate_collection.
Is there a way we could let MyActiveResource call the instantiate methods, by making them protected, for example?
My current workaround is creating my own get_record method to replace .get. However, it doesn't have a lot of the goodness that instantiate_record has, and is a pretty brittle solution all around
def get_record(path)
MyActiveResource.new(get(path))
end
Comments and changes to this ticket
-
jblanche July 22nd, 2008 @ 12:13 AM
- → Tag changed from “” to “activeresource enhancement”
I have searched a lot to solve this problem too but in fact there is no problem :)
You just have to write something like
@songs = Song.find(:all, :from => :list_by_artist, :params => {:artist_id => 2})
and you'll get your records instantiated.
-
Joshua Peek October 28th, 2008 @ 04:30 PM
- → State changed from “new” to “stale”
Staling out, please reopen if this is still a problem.
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Source available from github
The Git repository resides at http://github.com/rails
Check out the current development trunk (Edge Rails) with:
git clone git://github.com/rails/rails.git
Creating or reviewing a patch
See the contributor guide.
Creating a feature request
Please don't. If you want a new feature in Rails, you'll have to pull up your sleeves and get busy yourself. Or convince someone else to do it. See the contributor guide on how to get going. But posting them here is just going to lead to ticket root.
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.
Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too".
