Custom serializer fields in Django - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output of this custom serializer field?

Consider this Django REST Framework serializer field that converts a string to uppercase during serialization.
What will be the serialized output for the input {'name': 'alice'}?

Django

from rest_framework import serializers

class UpperCaseField(serializers.Field):
    def to_representation(self, value):
        return value.upper()

class UserSerializer(serializers.Serializer):
    name = UpperCaseField()

serializer = UserSerializer({'name': 'alice'})
print(serializer.data)

A Raises AttributeError

B {'name': 'alice'}

C {'name': 'Alice'}

D {'name': 'ALICE'}

💡 Hint

Look at what the to_representation method does to the input value.

The custom field overrides to_representation to convert the string to uppercase. So the output will have 'ALICE' as the name.

📝 Syntax

intermediate

Identify the syntax error in this custom serializer field

Which option correctly fixes the syntax error in this custom serializer field code?

Django

from rest_framework import serializers

class CustomField(serializers.Field):
    def to_representation(self, value)
        return str(value) + '!'

A Add a colon after the method definition: def to_representation(self, value):

B Change 'def' to 'function' in the method definition

C Remove 'self' parameter from the method

D Indent the return statement one level less

💡 Hint

Python method definitions require a colon at the end.

The method definition is missing a colon at the end, which causes a SyntaxError.

❓ state_output

advanced

What is the value of 'data' after serialization?

Given this serializer with a custom field that reverses strings during serialization, what is the value of serializer.data?

Django

from rest_framework import serializers

class ReverseField(serializers.Field):
    def to_representation(self, value):
        return value[::-1]

class MessageSerializer(serializers.Serializer):
    message = ReverseField()

serializer = MessageSerializer({'message': 'hello'})
data = serializer.data

A {'message': 'olleh'}

B Raises TypeError

C {'message': 'HELLO'}

D {'message': 'hello'}

💡 Hint

The to_representation method reverses the string.

The custom field reverses the string 'hello' to 'olleh' during serialization.

🔧 Debug

advanced

Which option causes a runtime error when using this custom serializer field?

This custom field expects an integer but receives a string. Which option will cause a runtime error when serializing?

Django

from rest_framework import serializers

class DoubleIntegerField(serializers.Field):
    def to_representation(self, value):
        return value * 2

class NumberSerializer(serializers.Serializer):
    number = DoubleIntegerField()

serializer = NumberSerializer({'number': input_value})
output = serializer.data

A input_value = '5'

B input_value = None

C input_value = 5

D input_value = 3.5

💡 Hint

Consider what happens when None is multiplied by 2.

Multiplying None by 2 raises a TypeError because NoneType cannot be multiplied.

🧠 Conceptual

expert

Which option correctly implements a custom serializer field that validates input as a positive integer?

You want to create a custom serializer field that only accepts positive integers during input validation. Which option correctly implements the to_internal_value method to enforce this?

A

def to_internal_value(self, data):
    value = int(data)
    if value < 0:
        raise serializers.ValidationError('Must be positive')
    return value

B

def to_internal_value(self, data):
    if data > 0:
        return data
    else:
        raise serializers.ValidationError('Must be positive')

C

def to_internal_value(self, data):
    value = int(data)
    if value <= 0:
        raise serializers.ValidationError('Must be positive')
    return value

D

def to_internal_value(self, data):
    value = float(data)
    if value <= 0:
        raise serializers.ValidationError('Must be positive')
    return value

💡 Hint

Remember to convert input to int and check for positive values including zero.

Option C converts input to int, checks if value is less than or equal to zero, and raises error if so. This correctly enforces positive integers (greater than zero).

Practice

1. What is the main purpose of creating a custom serializer field in Django REST Framework?

easy

A. To style the API response with CSS

B. To create new database tables automatically

C. To handle user authentication and permissions

D. To control how data is converted to and from JSON format

Solution

1. Step 1: Understand serializer fields role

   Serializer fields define how data is transformed between Python objects and JSON.

2. Step 2: Identify custom field purpose

   Custom fields let you control this transformation, especially for special data formats.

3. Final Answer:

   To control how data is converted to and from JSON format -> Option D

4. Quick Check:

   Custom serializer fields = control data format [OK]

Hint: Custom fields change data format in API input/output [OK]

Common Mistakes:

• Confusing serializer fields with database models
• Thinking custom fields handle authentication
• Assuming styling is done in serializers

2. Which method should you override in a custom serializer field to change how data is shown in API responses?

easy

A. to_internal_value

B. to_representation

C. validate

D. create

Solution

1. Step 1: Recall method roles in serializer fields

   to_representation converts Python data to JSON output; to_internal_value converts input JSON to Python.

2. Step 2: Identify output formatting method

   To change API response format, override to_representation.

3. Final Answer:

   to_representation -> Option B

4. Quick Check:

   Output formatting = to_representation [OK]

Hint: Output uses to_representation method [OK]

Common Mistakes:

• Using to_internal_value for output formatting
• Confusing validate with data conversion
• Overriding create instead of serialization methods

3. Given this custom serializer field code, what will be the output for input value 10?

class DoubleField(serializers.Field):
    def to_representation(self, value):
        return value * 2

field = DoubleField()
print(field.to_representation(10))

medium

A. 20

B. '10'

C. 10

D. Error

Solution

1. Step 1: Analyze to_representation method

   The method multiplies the input value by 2 before returning it.

2. Step 2: Calculate output for input 10

   10 * 2 = 20, so the output is 20.

3. Final Answer:

   20 -> Option A

4. Quick Check:

   10 doubled = 20 [OK]

Hint: to_representation transforms output value [OK]

Common Mistakes:

• Expecting input unchanged
• Confusing output type as string
• Assuming method raises error

4. Identify the error in this custom serializer field code:

class UpperCaseField(serializers.Field):
    def to_internal_value(self, data):
        return data.upper()

field = UpperCaseField()
print(field.to_internal_value(None))

medium

A. Field class must inherit from serializers.CharField

B. to_internal_value should return lowercase string

C. Calling upper() on None causes an AttributeError

D. to_internal_value method is missing a return statement

Solution

1. Step 1: Check method call on input

   The code calls data.upper() but data is None, which has no upper() method.

2. Step 2: Identify error type

   This causes an AttributeError at runtime.

3. Final Answer:

   Calling upper() on None causes an AttributeError -> Option C

4. Quick Check:

   None.upper() = AttributeError [OK]

Hint: Check input type before calling string methods [OK]

Common Mistakes:

• Assuming None is valid string input
• Thinking inheritance must be CharField
• Missing return statement (actually present)

5. You want to create a custom serializer field that accepts a comma-separated string of numbers and outputs a list of integers. Which methods should you override and how?

hard

A. Override to_internal_value to split and convert input string; override to_representation to join list into string

B. Override to_representation to split input string; override to_internal_value to join list

C. Override validate to convert string to list; no need to override to_representation

D. Override create method to parse string; override update to format list

Solution

1. Step 1: Understand input and output roles

   Input is a string (comma-separated), so to_internal_value must parse it into a list of integers.

2. Step 2: Format output for API response

   to_representation should convert the list back into a comma-separated string for output.

3. Final Answer:

   Override to_internal_value to split and convert input string; override to_representation to join list into string -> Option A

4. Quick Check:

   Input parsing = to_internal_value, output formatting = to_representation [OK]

Hint: Parse input in to_internal_value, format output in to_representation [OK]

Common Mistakes:

• Swapping input/output methods
• Using validate instead of conversion methods
• Overriding create/update which are unrelated