Marcin, that's exactly where I'm stuck! I know endpoints should never be 1:1 serialization of models, but I just don't know how to do that. I mean, I've been able to create endpoints like "/customers/1/payments/" where I use model relationships to generate JSON structures where Customer contains a Payments array field. My Address endpoint seems to be an oddity, as API consumers don't expect the city to contain state and the state to contain country as a JSON structure. How can I add these to the top-level Address entity directly while serialization? That's where I have no answers. Would it be possible for you to point me towards some article that does that? Thanks in advance!
Regards, Ankush On Monday, February 27, 2017 at 3:41:49 AM UTC+5:30, [email protected] wrote: > > > > On Tuesday, February 21, 2017 at 8:13:25 PM UTC+1, Ankush Thakur wrote: >> >> If the relationship chain was even deeper, there would be even more >> nesting, which I feel isn't great for API consumers. What is the best >> practice here to put state and country at the same level as the city? >> > > Just follow REST design. > Forget django models, think about encapsulation. > Think about representation of a resource, not about serializing a model(s). > Make semantic representations, as good as possible. > > You are not forced to do any nested nasty things. This has nothing to do > with REST api. > You may feel that DRF is limiting you. You'll be on a good path, if so. :) > > Good luck! > Marcin > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/70189b7c-69db-4b3a-9c3e-935121b76ea9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
