// the take
A serializer mixin for Django REST Framework that lets you create and update nested related objects (OneToOne, FK, M2M, GenericRelation) through a single parent serializer instead of writing manual create()/update() overrides. It's for anyone building a DRF API where the frontend posts a nested JSON blob and expects it to fan out into multiple related rows in one request.
Covers the full set of relation types DRF normally makes you handle by hand, including reverse FK and reverse OneToOne, which is the part people usually get wrong first. The CreateMixin/UpdateMixin split lets you opt into just one direction instead of inheriting behavior you don't want. UniqueFieldsMixin fixes a real, well-documented DRF footgun where UniqueValidator fires before the nested save, moving it to save-time instead. It's still getting releases that track current Django and DRF versions, not an abandoned 2018 package.
No support for M2M through models, which is the M2M case that actually needs custom fields most of the time, so you're back to manual serializer code exactly when the relation gets interesting. The documented workaround for form-data/multipart updates is to stuff nested data into a single field as a JSON string and json.loads() it in the view before calling super().update() — that's a hack living in the official README, not an edge case. Saving a nested payload loops over each related object and calls .save() individually, so a deeply nested request can mean a lot of sequential queries with no bulk-insert path. Partial-update semantics for nested lists (what happens to items omitted from the payload) aren't obvious from the serializer API and you end up reading mixins.py to find out.
We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →