I play with django-rest-framework and I would do following:
from rest_framework import serializers
from .models import Author, Book
class BookSerializer(serializers.ModelSerializer):
author = AuthorSerializer(many=False)
class Meta:
model = Book
fields = ('slug', 'name')
class AuthorSerializer(serializers.ModelSerializer):
books = BookSerializer(many=True)
class Meta:
model = Author
fields = ('slug', 'name', 'books')
But it fails.
NameError at /api/books/authors/
name 'AuthorSerializer' is not defined
Anybody helps?
When the file is imported, it's content is executed from top to bottom. So the line
author = AuthorSerializer(many=False)
tries to instantiate theAuthorSerializer
class before it is defined.Even if you could fix the circular dependency problem, it would be bad design. Whenever you serialize an Author, you include a list of all his books, which in turn include the Author object with it's list of books. This will result in another error for exceeding the recursion depth limit.
What you need to decide is in which direction you want to keep the included serialization: do you want the full Author object in each book serialization, or do you want the list of books with all its information for each Author object?
The reverse relation can then be included using any form of
RelatedField
as provided by the Django REST Framework.I know the question is pretty old, but I found a simple solution.
You need to define auxiliary serializers to handle the reference both ways:
This way you can use
BookSerializer
andAuthorSerializer
without infinite circular dependency of a Book having an Author who has Books which have Author who has Books...A workaround is to use serializers.SerializerMethodField():