URL fields in serializers – Django REST Framework

In Django REST Framework the very concept of Serializing is to convert DB data to a datatype that can be used by javascript. Every serializer comes with some fields (entries) which are going to be processed. For example if you have a class with name Employee and its fields as Employee_id, Employee_name, is_admin, etc. Then, you would need AutoField, CharField and BooleanField for storing and manipulating data through Django. Similarly, serializer also works with same principle and has fields that are used to create a serializer. 
This article revolves around URL Fields in Serializers in Django REST Framework. There are two major fields – URLField and SlugField.

URLField

URLField is basically a RegexField that validates the input against a URL matching pattern. Expects fully qualified URLs of the form http:///. It works the same as URLField – Django Models
It has the following arguments – 

• allow_blank – If set to True then the empty string should be considered a valid value. If set to False then the empty string is considered invalid and will raise a validation error. Defaults to False.

Syntax – 

field_name = serializers.URLField(*args, **kwargs)

SlugField

SlugField is a RegexField that validates the input against the pattern [a-zA-Z0-9_-]+. It is same as SlugField – Django Models.
Syntax – 

field_name = serializers.SlugField(*args, **kwargs)

How to use URL Fields in Serializers ?

To explain the usage of URL Fields, let’s use the same project setup from – How to Create a basic API using Django Rest Framework ?. 
Now that you have a file called serializers in your project, let’s create a serializer with URLField and SlugField as the fields. 

Python3

# import serializer from rest_framework
from rest_framework import serializers

class Geeks(object):
    def __init__(self, URL, slug):
        self.URL = URL
        self.slug = slug

# create a serializer
class GeeksSerializer(serializers.Serializer):
    # initialize fields
    URL = serializers.URLField()
    slug = serializers.SlugField()

Now let us create some objects and try serializing them and check if they are actually working, Run, – 

Python manage.py shell

Now, run following python commands in the shell 

# import everything from serializers
>>> from apis.serializers import *

# create a object of type Geeks
>>> obj = Geeks("https://www.geeksforgeeks.org/", "bring-out-the-geek-in-you-during-covid-19-outb
reak")

# serialize the object
>>> serializer = GeeksSerializer(obj)

# print serialized data
>>> serializer.data
{'URL': 'https://www.geeksforgeeks.org/', 'slug': 'bring-out-the-geek-in-you-during-covid-19-out
break'}

Here is the output of all these operations on terminal – 

Validation on URL Fields

Note that prime motto of these fields is to impart validations, such as URLField validates the data to URL only. Let’s check if these validations are working or not – 

# Create a dictionary and add invalid values
>>> data={}
>>> data['URL']="invalid_url"
>>> data['slug'] = "INVALID SLUG"

# dictionary created
>>> data
{'URL': 'invalid_url', 'slug': 'INVALID SLUG'}

# deserialize the data
>>> serializer = GeeksSerializer(data=data)

# check if data is valid
>>> serializer.is_valid()
False

# check the errors
>>> serializer.errors
{'URL': [ErrorDetail(string='Enter a valid URL.', code='invalid')], 
'slug': [ErrorDetail(string='Enter a valid "slug" consisting of letters, numbers,
underscores or hyphens.', code='invalid')]
}

Here is the output of these commands which clearly shows email and phone_number as invalid – 

Advanced concepts

Validations are part of Deserialization and not serialization. As explained earlier, serializing is process of converting already made data into another data type, so there is no requirement of these default validations out there. Deserialization requires validations as data needs to be saved to database or any more operation as specified. So if you serialize data using these fields that would work. 

Core arguments in serializer fields

.math-table { border-collapse: collapse; width: 100%; } .math-table td { border: 1px solid #5fb962; text-align: left !important; padding: 8px; } .math-table th { border: 1px solid #5fb962; padding: 8px; } .math-table tr>th{ background-color: #c6ebd9; vertical-align: middle; } .math-table tr:nth-child(odd) { background-color: #ffffff; } 

Argument	Description
read_only	Set this to True to ensure that the field is used when serializing a representation, but is not used when creating or updating an instance during deserialization
write_only	Set this to True to ensure that the field may be used when updating or creating an instance, but is not included when serializing the representation.
required	Setting this to False also allows the object attribute or dictionary key to be omitted from output when serializing the instance.
default	If set, this gives the default value that will be used for the field if no input value is supplied.
allow_null	Normally an error will be raised if None is passed to a serializer field. Set this keyword argument to True if None should be considered a valid value.
source	The name of the attribute that will be used to populate the field.
validators	A list of validator functions which should be applied to the incoming field input, and which either raise a validation error or simply return.
error_messages	A dictionary of error codes to error messages.
label	A short text string that may be used as the name of the field in HTML form fields or other descriptive elements.
help_text	A text string that may be used as a description of the field in HTML form fields or other descriptive elements.
initial	A value that should be used for pre-populating the value of HTML form fields.