4 ms·
If you're fighting the framework, you're doing it wrong. It is trivial to use serializers for non-ORM stuff. It is trivial to not use serializers at all. It is
by Daishiman 9y ago
If you're fighting the framework, you're doing it wrong.
It is trivial to use serializers for non-ORM stuff. It is trivial to not use serializers at all. It is trivial to plug your own auth and permissions.
- StavrosK 9y agoI'm a heavy Django user, and have used DRF occasionally. I find Django extremely pluggable and extensible, but I needed to write an API with DRF that didn't map cleanly onto the database models, and that was pretty cumbersome. DRF doesn't like it when you do things that don't map to the models, and the documentation is pretty bad. I had to read the source in the end to figure out how to do what I wanted, and I got the sense that I was lucky it was doable. If your database models map to your CRUD endpoints, though, everything is super easy.
- theptip 9y agoI use a lot of custom Serializers (not tied to any Model), and lots of SerializerMethodFields to selectively override generated ModelSerializer fields; this can get you quite far. I agree with your point that the further afield you go, the less you gain from the framework, though.
- StavrosK 9y agoThat's what I ended up doing, if I recall correctly, but the docs on this were pretty much non existent.