Oh, my apologies. I think I understand you better now. it was a direct
foreign key that I managed to get it to work with.. Just tried it with a
many-to-many field and as you point out it doesn't like it. I'll go back
to using json. I suppose i would change my doc request to a warning -
per
Thanks for the response :)
We are currently building our forms using React on the front end - not
using DRF to generate the forms - but we are using DRF's views and
serializers. So there are no problems with DRF's forms or the browsable
api.
I opted to use a writable nested serializer to try
Hi Daniel
> Le 5 juin 2016 à 10:30, Daniel Haggard a écrit :
>
> Hi folks,
>
> I had this issue recently where I had a writeable serializer nesting User
> info under the key 'owner', that was passing validation (because it contained
> the owner related data) but then removing the entire owner
