-
Notifications
You must be signed in to change notification settings - Fork 130
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
expose collection cannot specify a :serializer #110
Comments
I would also like to see this addressed |
Having a look now, I'll tweak it slightly and see if this can fix it - It's also an issue (I believe) with paginated collections. |
Oh, and the short way - If you specify |
actually my requirement was very simple, so I didn't find the correct way to do it. I just added below code to all model class then solved. doesn't need
|
I'm working on support for this at the moment - there are a few edge cases we need to keep in mind when doing so & hence I figured I'd update here:
This'll be pushed out in the newest release, apologies for the massive delays. |
@Sutto Agree with your comments. |
@Sutto is there any progress? |
@DmitryKK there hadn't been, but going to do this for 1.12 in the next few days |
Try the version in master - I just pushed rough support for this. |
Thanks, i tried. Serializer works only for the first record |
Have you got a specific example of what you're doing so I can try again? On Tue, May 19, 2015 at 8:52 AM -0700, "Dmitry Krakosevich" [email protected] wrote: Thanks, i tried. Serializer works only for the first record — |
All good - Fixed and pushed |
v1.12 is out now which fixes this. Thanks all! |
Perfect! Thank you very much |
If I wants to expose a array of objects, each one can use a serializer, but I didn't find any
:each_serializer
option there.What I should do?
I made a pull request, it works for me, but I am not sure if it is the correct solution.
#106
The text was updated successfully, but these errors were encountered: