Function-based vs class-based decision in Django - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a function-based view that returns a simple HTTP response.

Django

from django.http import HttpResponse

def my_view(request):
    return [1]("Hello, world!")

Drag options to blanks, or click blank then click option'

Arender

BHttpResponse

Credirect

DJsonResponse

Attempts:

3 left

💡 Hint

Common Mistakes

Using render instead of HttpResponse for simple text response

Forgetting to return the response object

The function-based view returns an HttpResponse object with the text.

2fill in blank

medium

Complete the code to import the base class for class-based views.

Django

from django.views import [1]

Drag options to blanks, or click blank then click option'

ATemplateView

BHttpResponse

CView

DListView

Attempts:

3 left

💡 Hint

Common Mistakes

Importing a specific view class instead of the base View

Confusing HttpResponse with a view class

The base class for all class-based views is View from django.views.

3fill in blank

hard

Fix the error in the class-based view by completing the method name that handles GET requests.

Django

from django.views import View
from django.http import HttpResponse

class MyView(View):
    def [1](self, request):
        return HttpResponse("Hello from class-based view")

Drag options to blanks, or click blank then click option'

Adispatch

Bhandle

Cpost

Dget

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'post' instead of 'get' for GET requests

Using 'dispatch' directly instead of 'get'

The method to handle GET requests in a class-based view is named get.

4fill in blank

hard

Fill both blanks to complete a function-based view that renders a template with context.

Django

from django.shortcuts import [1]

def home(request):
    context = {'name': 'Alice'}
    return [2](request, 'home.html', context)

Drag options to blanks, or click blank then click option'

Arender

BHttpResponse

Credirect

Dget_object_or_404

Attempts:

3 left

💡 Hint

Common Mistakes

Importing render but returning HttpResponse directly

Using redirect instead of render for templates

The render shortcut both imports and returns a rendered template with context.

5fill in blank

hard

Fill all three blanks to complete a class-based view that renders a template with extra context.

Django

from django.views.generic import [1]

class WelcomeView([2]):
    template_name = 'welcome.html'

    def get_context_data(self, **kwargs):
        context = super().[3](**kwargs)
        context['user'] = 'Bob'
        return context

Drag options to blanks, or click blank then click option'

ATemplateView

BView

Cget_context_data

Ddispatch

Attempts:

3 left

💡 Hint

Common Mistakes

Using View instead of TemplateView for template rendering

Calling super().dispatch instead of super().get_context_data

TemplateView is used to render templates in class-based views. The method get_context_data adds extra data to the template context.

Practice

1. Which of the following is a key advantage of using class-based views (CBVs) over function-based views (FBVs) in Django?

easy

A. FBVs require less code for complex views.

B. CBVs are always faster than FBVs.

C. FBVs cannot handle POST requests.

D. CBVs allow reuse of common functionality through inheritance.

Solution

1. Step 1: Understand CBVs and inheritance

   Class-based views use classes, so they can inherit and reuse code easily.

2. Step 2: Compare with FBVs

   Function-based views are simple functions and do not support inheritance for reuse.

3. Final Answer:

   CBVs allow reuse of common functionality through inheritance. -> Option D

4. Quick Check:

   CBVs = reuse by inheritance [OK]

Hint: CBVs use classes, so they support inheritance and reuse [OK]

Common Mistakes:

• Thinking CBVs are always faster
• Believing FBVs can't handle POST
• Assuming FBVs are better for complex views

2. Which of the following is the correct way to define a simple function-based view in Django?

easy

A. def my_view(request): return HttpResponse('Hello')

B. class my_view(View): return HttpResponse('Hello')

C. def my_view(): return HttpResponse('Hello')

D. class my_view: def get(): return HttpResponse('Hello')

Solution

1. Step 1: Check function signature for FBV

   A function-based view must accept a request parameter.

2. Step 2: Validate return statement

   The function should return an HttpResponse object.

3. Final Answer:

   def my_view(request): return HttpResponse('Hello') -> Option A

4. Quick Check:

   FBV needs request param and returns HttpResponse [OK]

Hint: FBVs are functions with request parameter returning HttpResponse [OK]

Common Mistakes:

• Omitting the request parameter
• Using class syntax for FBV
• Not returning HttpResponse

3. Given this class-based view code, what will be the HTTP response content when a GET request is made?

from django.http import HttpResponse
from django.views import View

class HelloView(View):
    def get(self, request):
        return HttpResponse('Hello from CBV')

medium

A. HelloView object

B. Hello from CBV

C. Error: get method missing request

D. Empty response

Solution

1. Step 1: Identify the get method behavior

   The get method returns HttpResponse with 'Hello from CBV'.

2. Step 2: Understand request handling

   A GET request calls the get method and returns that response content.

3. Final Answer:

   Hello from CBV -> Option B

4. Quick Check:

   GET calls get() returning 'Hello from CBV' [OK]

Hint: GET calls get() method in CBV returning its HttpResponse [OK]

Common Mistakes:

• Confusing class name with response content
• Thinking get method lacks request parameter
• Expecting empty or error response

4. What is wrong with this function-based view code?

def my_view():
    return HttpResponse('Hi')

medium

A. Function name must be capitalized.

B. HttpResponse cannot be returned from a function.

C. Missing request parameter in function definition.

D. The return statement should be inside a class.

Solution

1. Step 1: Check function parameters

   Function-based views must accept a request parameter to receive HTTP requests.

2. Step 2: Validate function signature

   The given function lacks the required request parameter, causing errors.

3. Final Answer:

   Missing request parameter in function definition. -> Option C

4. Quick Check:

   FBV needs request param [OK]

Hint: FBVs always need request parameter [OK]

Common Mistakes:

• Ignoring missing request parameter
• Thinking HttpResponse can't be returned
• Believing function names must be capitalized

5. You want to create a Django view that handles GET and POST requests differently and also reuse some common code for multiple views. Which approach is best?

hard

A. Use class-based views with methods for GET and POST and inheritance for reuse.

B. Use class-based views but define all logic in a single method.

C. Use function-based views with if-else inside to check request method.

D. Use function-based views with decorators for GET and POST.

Solution

1. Step 1: Identify need for handling GET and POST separately

   Class-based views allow defining separate get() and post() methods for clarity.

2. Step 2: Consider code reuse

   CBVs support inheritance, so common code can be reused across multiple views easily.

3. Final Answer:

   Use class-based views with methods for GET and POST and inheritance for reuse. -> Option A

4. Quick Check:

   CBVs = separate methods + reuse [OK]

Hint: CBVs separate methods and support inheritance for reuse [OK]

Common Mistakes:

• Using FBVs with complex if-else for methods
• Putting all logic in one CBV method
• Ignoring inheritance benefits