-
Notifications
You must be signed in to change notification settings - Fork 182
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
API RF: Improve the way nested relationships are stored #202
Comments
@ecoslado why not use Fast JSON Api? |
That could be definitively a good option. Right now I'm working on upgrading to Rails 5, but after that this could be done. |
@peillis I have a forked Rails 5.2 version in production |
Great! but where is the code? I can't see any of it in your account. |
I made it private because I added additional ERP functionality and commit confidential information by accident but I'll make a PR for the 5.2 portion of the upgrade |
Dont worry about it, I have the work almost done. Thank you
El vie., 19 jul. 2019 20:03, Dane Wilson <notifications@github.com>
escribió:
… I made it private because I added additional ERP functionality and commit
confidential information by accident but I'll make a PR for the 5.2 portion
of the upgrade
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/siwapp/siwapp/issues/202?email_source=notifications&email_token=AADQR3NWEF3LVNBN5OVZZWTQAH6YLA5CNFSM4CVBA4A2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2MK5XA#issuecomment-513322716>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADQR3NH3EMEKXK7KYQZD7LQAH6YLANCNFSM4CVBA4AQ>
.
|
I've changed the API to implement JSON API Standard. I used ActiveModel Serializers to do that, but I didn't find the way to make the serializer to store nested relationships in objects. So, in commons_controller.rb, I add every relationship explicitly:
https://github.com/siwapp/siwapp/blob/master/app/controllers/api/v1/commons_controller.rb#L49
Look for a cleaner solution.
The text was updated successfully, but these errors were encountered: