Safe navigation operator for null in Angular - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to safely access the name property of user.

Angular

<p>{{ user[1]name }}</p>

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

A.

B?.

C->

D::

Attempts:

3 left

💡 Hint

Common Mistakes

Using the normal dot operator causes errors if the object is null.

Using arrow or double colon operators which are not valid in Angular templates.

The safe navigation operator ?. prevents errors if user is null or undefined.

2fill in blank

medium

Complete the code to safely call the getAddress() method on customer.

Angular

<p>{{ customer[1]getAddress() }}</p>

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

A?.

B.

C::

D->

Attempts:

3 left

💡 Hint

Common Mistakes

Using the normal dot operator causes runtime errors if customer is null.

Using invalid operators like double colon or arrow.

The safe navigation operator ?. safely calls the method only if customer is not null.

3fill in blank

hard

Fix the error in safely accessing profile.email when profile might be null.

Angular

<p>{{ profile[1]email }}</p>

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

A->

B::

C.

D?.

Attempts:

3 left

💡 Hint

Common Mistakes

Using the normal dot operator causes errors if profile is null.

Trying to use unsupported operators.

Using ?. prevents errors if profile is null by safely accessing email.

4fill in blank

hard

Fill both blanks to safely access order.details.price when order or details might be null.

Angular

<p>{{ order[1]details[2]price }}</p>

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

A?.

B.

C::

D->

Attempts:

3 left

💡 Hint

Common Mistakes

Using normal dot operator causes errors if any object in the chain is null.

Mixing safe navigation with normal dot operator incorrectly.

Using ?. twice safely accesses nested properties even if order or details is null.

5fill in blank

hard

Fill all three blanks to safely access data.user.profile.email when any object might be null.

Angular

<p>{{ data[1]user[2]profile[3]email }}</p>

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

A.

B?.

C::

D->

Attempts:

3 left

💡 Hint

Common Mistakes

Using normal dot operator causes errors if any object is null.

Using unsupported operators like double colon or arrow.

Using the safe navigation operator ?. at each step prevents errors if any object is null.

Practice

1. What does the safe navigation operator ?. do in Angular templates?

easy

A. Prevents errors when accessing properties of null or undefined objects

B. Automatically initializes null objects

C. Converts null values to empty strings

D. Throws an error if a property is null

Solution

1. Step 1: Understand the purpose of the safe navigation operator

   The operator ?. is used to safely access properties on objects that might be null or undefined, avoiding runtime errors.

2. Step 2: Identify what happens without it

   Without ?., accessing a property on null or undefined causes an error and breaks the app.

3. Final Answer:

   Prevents errors when accessing properties of null or undefined objects -> Option A

4. Quick Check:

   Safe navigation operator = prevents null errors [OK]

Hint: Think: "Safe access avoids crashes" [OK]

Common Mistakes:

• Assuming it initializes null objects
• Thinking it converts null to empty string
• Believing it throws errors on null

2. Which of the following is the correct syntax to safely access the name property of a possibly null user object in an Angular template?

easy

A. {{ user?.name }}

B. {{ user.name }}

C. {{ user:name }}

D. {{ user->name }}

Solution

1. Step 1: Recall the safe navigation syntax

   The safe navigation operator is ?., used as object?.property to avoid errors if object is null.

2. Step 2: Match the syntax to the options

   {{ user?.name }} uses user?.name, which is correct. Options A, C, and D use invalid or unsafe syntax.

3. Final Answer:

   {{ user?.name }} -> Option A

4. Quick Check:

   Safe access uses ?. operator [OK]

Hint: Look for ?. between object and property [OK]

Common Mistakes:

• Omitting the ? operator
• Using colon or arrow instead of ?.
• Confusing with other operators

3. Given the component property user = null;, what will be the output of this Angular template snippet?

{{ user?.name || 'Guest' }}

medium

A. undefined

B. Guest

C. null

D. Error

Solution

1. Step 1: Evaluate safe navigation on null

   Since user is null, user?.name safely returns undefined without error.

2. Step 2: Apply the logical OR operator

   The expression undefined || 'Guest' evaluates to 'Guest' because undefined is falsy.

3. Final Answer:

   Guest -> Option B

4. Quick Check:

   Safe navigation returns undefined, fallback used [OK]

Hint: Safe navigation returns undefined, use || for fallback [OK]

Common Mistakes:

• Expecting an error on null access
• Thinking output is 'null' string
• Ignoring fallback with || operator

4. Identify the error in this Angular template snippet:

{{ user?.address.city }}

where user can be null or have address as null.

medium

A. No error, safe navigation is used correctly

B. Error because safe navigation operator cannot be chained

C. Error because city is accessed without safe navigation

D. Error because user is not checked for null

Solution

1. Step 1: Analyze safe navigation usage

   The snippet uses user?.address.city. The safe navigation is only before address, not before city.

2. Step 2: Identify potential null access

   If user is not null but address is null, accessing city without safe navigation causes an error.

3. Final Answer:

   Error because city is accessed without safe navigation -> Option C

4. Quick Check:

   Chain safe navigation for nested nulls [OK]

Hint: Use ?. before each nested property to avoid errors [OK]

Common Mistakes:

• Assuming one ?. covers all nested properties
• Ignoring null possibility of nested objects
• Thinking chaining ?. is invalid syntax

5. You have a nested object profile which may be null or have null nested properties. How would you safely display the profile.contact.email in the template, showing 'No Email' if any part is null?

hard

A. {{ profile?.contact?.email ? 'No Email' : profile.contact.email }}

B. {{ profile.contact.email || 'No Email' }}

C. {{ profile?.contact.email || 'No Email' }}

D. {{ profile?.contact?.email || 'No Email' }}

Solution

1. Step 1: Use safe navigation for each nested property

   Since profile and contact can be null, use ?. before both contact and email.

2. Step 2: Provide fallback text for null or undefined

   Use || 'No Email' to show fallback if the email is missing.

3. Final Answer:

   {{ profile?.contact?.email || 'No Email' }} -> Option D

4. Quick Check:

   Chain ?. and use || fallback [OK]

Hint: Chain ?. for nested nulls, use || for fallback [OK]

Common Mistakes:

• Missing ?. on nested properties
• Using ternary incorrectly for fallback
• Not handling null nested objects