Why class-based views exist in Django - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

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

Django

from django.views import [1]

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

AView

BModel

CTemplate

DForm

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Model' which is for database models, not views.

Using 'Template' or 'Form' which are unrelated to base view classes.

The base class for class-based views in Django is View. It provides the foundation to build views as classes.

2fill in blank

medium

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

Django

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

class HelloView(View):
    def [1](self, request):
        return HttpResponse('Hello!')

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

Arender

Bpost

Cinit

Dget

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'post' when the view is meant to handle GET requests.

Using 'init' which is a constructor, not a request handler.

The get method handles HTTP GET requests in class-based views.

3fill in blank

hard

Fix the error in the class-based view method signature to correctly accept the request and return a response.

Django

class MyView(View):
    def get([1]):
        return HttpResponse('Hi')

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

Arequest

Brequest, self

Cself, request

Dself

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting self parameter.

Placing request before self.

Instance methods in Python classes must have self as the first parameter, followed by request for Django views.

4fill in blank

hard

Fill both blanks to create a dictionary comprehension that maps words to their lengths only if length is greater than 3.

Django

lengths = {word: [1] for word in words if len(word) [2] 3}

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

Alen(word)

B<

C>

Dword

Attempts:

3 left

💡 Hint

Common Mistakes

Using '<' instead of '>' in the condition.

Mapping word to word itself instead of its length.

The dictionary maps each word to its length using len(word). The condition filters words with length greater than 3 using >.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that maps uppercase keys to values only if value is positive.

Django

result = [1]: [2] for k, v in data.items() if v [3] 0}

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

Ak.upper()

Bv

C>

Dk

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'k' instead of 'k.upper()' for keys.

Using '<' instead of '>' in the condition.

Swapping keys and values in the comprehension.

The keys are converted to uppercase with k.upper(). The values are kept as v. The condition filters values greater than zero using >.

Practice

1. Why do Django developers use class-based views instead of function-based views?

easy

A. Because function-based views are not supported in Django

B. Because class-based views automatically generate HTML templates

C. To avoid writing any code for handling requests

D. To organize related request handling methods in one place for better reuse

Solution

1. Step 1: Understand the purpose of class-based views

   Class-based views group related HTTP method handlers (like GET, POST) inside one class, making code organized.

2. Step 2: Compare with function-based views

   Function-based views handle requests with single functions, which can get messy when handling many request types.

3. Final Answer:

   To organize related request handling methods in one place for better reuse -> Option D

4. Quick Check:

   Class-based views improve organization = B [OK]

Hint: Class-based views group related request methods together [OK]

Common Mistakes:

• Thinking function-based views are deprecated
• Believing class-based views auto-generate templates
• Assuming class-based views remove need to write request code

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

easy

A. class MyView(View): def get(self, request): return HttpResponse('Hello')

B. def MyView(request): return HttpResponse('Hello')

C. class MyView: def get(request): return 'Hello'

D. view MyView: def get(self, request): return HttpResponse('Hello')

Solution

1. Step 1: Recall Django class-based view syntax

   A class-based view inherits from django.views.View and defines methods like get(self, request).

2. Step 2: Check each option

   class MyView(View): def get(self, request): return HttpResponse('Hello') correctly inherits View and defines get with self and request, returning HttpResponse.

3. Final Answer:

   class MyView(View): def get(self, request): return HttpResponse('Hello') -> Option A

4. Quick Check:

   Correct class-based view syntax = A [OK]

Hint: Class-based views inherit View and define methods with self [OK]

Common Mistakes:

• Forgetting to inherit from View
• Missing self parameter in methods
• Using invalid syntax like 'view' keyword

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 World')

medium

A. Hello World

B. Error: get method missing self

C. Empty response

D. HelloView object

Solution

1. Step 1: Analyze the get method in HelloView

   The get method returns HttpResponse with content 'Hello World'.

2. Step 2: Understand what happens on GET request

   When a GET request hits HelloView, the get method runs and returns 'Hello World' as response content.

3. Final Answer:

   Hello World -> Option A

4. Quick Check:

   GET request returns 'Hello World' = C [OK]

Hint: GET calls get() method returning HttpResponse content [OK]

Common Mistakes:

• Confusing method names or missing self
• Expecting object string instead of response content
• Assuming empty response without return

4. Identify the error in this class-based view code:

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

class MyView(View):
    def get(request):
        return HttpResponse('Hi')

medium

A. Class must inherit from HttpResponse

B. HttpResponse import is incorrect

C. Missing self parameter in get method

D. get method should be named post

Solution

1. Step 1: Check method signature in class-based views

   Instance methods must have self as first parameter; get(request) misses self.

2. Step 2: Verify other parts

   HttpResponse import is correct, inheritance is correct, method name get is valid for GET requests.

3. Final Answer:

   Missing self parameter in get method -> Option C

4. Quick Check:

   Instance methods need self parameter = A [OK]

Hint: Instance methods always need self as first parameter [OK]

Common Mistakes:

• Omitting self in method definitions
• Confusing inheritance requirements
• Renaming get method incorrectly

5. You want to create a Django class-based view that handles both GET and POST requests differently. Which approach best uses class-based views to keep code clean and reusable?

hard

A. Create two classes each with only get method and post method respectively

B. Define get(self, request) and post(self, request) methods inside one class inheriting from View

C. Use one method to handle both GET and POST by checking request.method inside it

D. Write separate function-based views for GET and POST and link URLs accordingly

Solution

1. Step 1: Understand class-based view design for multiple HTTP methods

   Class-based views allow defining separate methods like get and post in one class for clarity and reuse.

2. Step 2: Evaluate options for clean, reusable code

   Define get(self, request) and post(self, request) methods inside one class inheriting from View keeps related logic together, making code organized and easy to extend.

3. Final Answer:

   Define get(self, request) and post(self, request) methods inside one class inheriting from View -> Option B

4. Quick Check:

   Separate methods in one class for HTTP verbs = D [OK]

Hint: Use separate get/post methods in one class for clarity [OK]

Common Mistakes:

• Splitting GET and POST into separate views unnecessarily
• Handling all methods in one function with if-else
• Creating multiple classes for each HTTP method