URL parameter type converters in Django - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to capture an integer parameter named 'year' in the URL pattern.

Django

path('archive/<[1]:year>/', views.archive, name='archive')

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

Astr

Buuid

Cint

Dslug

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'str' instead of 'int' which captures any string, not just numbers.

Using 'slug' which matches letters, numbers, underscores or hyphens.

The int converter captures integer values from the URL and passes them as integers to the view.

2fill in blank

medium

Complete the code to capture a slug parameter named 'post_slug' in the URL pattern.

Django

path('post/<[1]:post_slug>/', views.post_detail, name='post_detail')

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

Aslug

Bint

Cuuid

Dstr

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'int' which only matches numbers.

Using 'uuid' which expects a UUID format.

The slug converter matches letters, numbers, underscores, or hyphens, suitable for slugs.

3fill in blank

hard

Fix the error in the URL pattern to correctly capture a UUID parameter named 'user_id'.

Django

path('user/<[1]:user_id>/', views.user_profile, name='user_profile')

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

Auuid

Bstr

Cslug

Dint

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'str' which matches any string but does not validate UUID format.

Using 'int' which only matches numbers.

The uuid converter matches UUID strings and converts them to UUID objects.

4fill in blank

hard

Fill both blanks to capture a string parameter 'username' and an integer parameter 'page' in the URL pattern.

Django

path('profile/<[1]:username>/page/<[2]:page>/', views.profile_page, name='profile_page')

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

Astr

Bint

Cslug

Duuid

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'slug' for username which may exclude some characters.

Using 'str' for page which should be an integer.

The str converter captures any non-empty string for 'username', and int captures an integer for 'page'.

5fill in blank

hard

Fill all three blanks to create a URL pattern capturing a slug 'category', an integer 'year', and a UUID 'item_id'.

Django

path('shop/<[1]:category>/<[2]:year>/<[3]:item_id>/', views.shop_item, name='shop_item')

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

Aslug

Bint

Cuuid

Dstr

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up converters like using 'str' for year or 'int' for UUID.

Using 'slug' for year which expects numbers.

The slug converter captures the category text, int captures the year as a number, and uuid captures the item ID in UUID format.

Practice

1. What does the int converter do in a Django URL pattern?

easy

A. It matches any string including letters and symbols.

B. It matches only integer values and converts them to Python int type.

C. It matches UUID strings only.

D. It matches file paths including slashes.

Solution

1. Step 1: Understand the role of converters

   Converters tell Django what type of data to expect and convert URL parts accordingly.

2. Step 2: Identify the behavior of int converter

   The int converter matches only digits and converts them to Python integers.

3. Final Answer:

   It matches only integer values and converts them to Python int type. -> Option B

4. Quick Check:

   int converter = matches integers [OK]

Hint: int converter matches digits only, converts to int [OK]

Common Mistakes:

• Thinking int matches strings with letters
• Confusing int with slug or str converters
• Assuming int matches UUIDs

2. Which of the following is the correct syntax to capture a slug parameter named post_slug in a Django URL pattern?

easy

A. path('post//', views.post_detail)

B. path('post//', views.post_detail)

C. path('post//', views.post_detail)

D. path('post//', views.post_detail)

Solution

1. Step 1: Identify the correct converter for slugs

   The slug converter matches letters, numbers, underscores, and hyphens.

2. Step 2: Match syntax with converter and parameter name

   The syntax is <slug:post_slug> inside the path string.

3. Final Answer:

   path('post/<slug:post_slug>/', views.post_detail) -> Option A

4. Quick Check:

   slug converter syntax = <slug:name> [OK]

Hint: Use for slug parameters in URL patterns [OK]

Common Mistakes:

• Using int converter for slug parameters
• Mixing UUID or path converters incorrectly
• Missing colon between converter and parameter name

3. Given the URL pattern path('user//', views.profile) and the URL /user/42/, what will be the type and value of user_id in the view?

medium

A. A string '42'

B. A path string including slashes

C. A UUID object

D. An integer 42

Solution

1. Step 1: Analyze the URL pattern converter

   The int converter converts the URL part to an integer.

2. Step 2: Check the URL segment matched

   The URL segment '42' matches the int converter and becomes integer 42.

3. Final Answer:

   An integer 42 -> Option D

4. Quick Check:

   int converter converts to int type [OK]

Hint: int converter converts URL part to integer type [OK]

Common Mistakes:

• Assuming user_id is a string
• Confusing int with uuid or path converters
• Thinking the value includes slashes

4. What is wrong with this URL pattern? path('article//', views.detail) when the URL /article/abc/ is requested.

medium

A. No error, the view receives id='abc' as a string.

B. The pattern should use to accept 'abc'.

C. URL does not match because 'abc' is not an integer, causing a 404 error.

D. The view will raise a ValueError automatically.

Solution

1. Step 1: Understand the int converter behavior

   The int converter only matches digits; 'abc' is not digits.

2. Step 2: Check URL matching result

   Since 'abc' does not match int, Django returns a 404 error (no match).

3. Final Answer:

   URL does not match because 'abc' is not an integer, causing a 404 error. -> Option C

4. Quick Check:

   int converter rejects non-digit URL parts [OK]

Hint: int converter rejects non-digit URL parts, causing 404 [OK]

Common Mistakes:

• Thinking view gets string 'abc' anyway
• Expecting automatic type conversion errors in view
• Confusing 404 with server error

5. You want to capture a URL parameter that can include slashes, such as a file path, in Django. Which converter should you use and why?

hard

A. Use path converter because it matches any string including slashes.

B. Use str converter because it matches strings without slashes.

C. Use slug converter because it matches letters and hyphens.

D. Use uuid converter because it matches unique identifiers.

Solution

1. Step 1: Identify the need to match slashes in URL parameter

   Regular str converter stops at slashes, so it cannot capture paths with slashes.

2. Step 2: Choose the converter that allows slashes

   The path converter matches any string including slashes, perfect for file paths.

3. Final Answer:

   Use path converter because it matches any string including slashes. -> Option A

4. Quick Check:

   path converter = matches strings with slashes [OK]

Hint: Use path converter to capture URL parts with slashes [OK]

Common Mistakes:

• Using str converter which stops at slashes
• Confusing slug or uuid converters for paths
• Expecting int converter to match strings