*ngIf for conditional rendering in Angular - Step-by-Step Execution

Concept Flow - *ngIf for conditional rendering

Start

↓

Evaluate *ngIf condition

↓

Render element in DOM

↓

Do not render element

↓

End

Angular checks the *ngIf condition. If true, it adds the element to the page. If false, it removes or skips it.

Execution Sample

Angular

<div *ngIf="showMessage">Hello, Angular!</div>
<button (click)="toggle()">Toggle Message</button>

showMessage = true;

toggle() {
  this.showMessage = !this.showMessage;
}

This code shows or hides a message based on the showMessage variable toggled by a button.

Execution Table

Step	Action	*ngIf Condition (showMessage)	Render Element?	DOM Change
1	Initial render	true	Yes	Element <div>Hello, Angular!</div> added to DOM
2	User clicks button	true -> false	No	Element removed from DOM
3	User clicks button again	false -> true	Yes	Element added back to DOM
4	No further clicks	true	Yes	No change
Exit	No more actions	-	-	Rendering stable

💡 Execution stops when no more user clicks occur and DOM matches condition

Variable Tracker

Variable	Start	After 1	After 2	After 3	Final
showMessage	true	false	true	true	true

Key Moments - 3 Insights

Why does the element disappear when showMessage becomes false?

Because *ngIf removes the element from the DOM when the condition is false, as shown in execution_table step 2.

Does the element stay in the DOM but hidden when *ngIf is false?

No, *ngIf completely removes the element from the DOM, not just hides it. This is clear in execution_table step 2 where the element is removed.

What happens if the condition changes back to true?

The element is re-created and added back to the DOM, as seen in execution_table step 3.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of showMessage at step 2?

A undefined

B true

C false

D null

💡 Hint

Check variable_tracker row for showMessage at After 1 (step 2).

At which step does the element get removed from the DOM?

A Step 1

B Step 2

C Step 3

D Exit

💡 Hint

See execution_table DOM Change column for when element is removed.

If showMessage started as false, what would happen at initial render?

A Element would not be rendered

B Element would be rendered

C Error occurs

D Element rendered but hidden

💡 Hint

Recall *ngIf removes element if condition is false, as shown in execution_table step 2.

Concept Snapshot

*ngIf directive conditionally adds or removes elements from the DOM.
Syntax: <element *ngIf="condition">content</element>
If condition is true, element is rendered.
If false, element is removed completely.
Useful for showing/hiding UI based on variables.

Full Transcript

The *ngIf directive in Angular controls whether an element appears on the page. When Angular renders the page, it checks the condition inside *ngIf. If the condition is true, Angular adds the element to the page's DOM. If false, Angular removes the element entirely. For example, if showMessage is true, a message div is shown. When the user clicks a button, showMessage toggles between true and false. Each toggle causes Angular to add or remove the message element. This means the element is not just hidden but completely removed when the condition is false. When the condition becomes true again, Angular recreates and adds the element back. This behavior helps keep the page clean and efficient by only rendering what is needed.

Practice

1. What does the Angular directive *ngIf do in a template?

easy

A. It loops over a list and renders each item.

B. It styles an element dynamically.

C. It binds a variable to an input field.

D. It conditionally includes or removes an element from the DOM based on a boolean expression.

Solution

1. Step 1: Understand the purpose of *ngIf

   *ngIf is used to conditionally render elements in Angular templates.

2. Step 2: Identify what *ngIf controls

   It controls whether an element is included or removed from the DOM based on a true or false condition.

3. Final Answer:

   It conditionally includes or removes an element from the DOM based on a boolean expression. -> Option D

4. Quick Check:

   *ngIf = conditional rendering [OK]

Hint: Remember *ngIf shows or hides elements by condition [OK]

Common Mistakes:

• Confusing *ngIf with *ngFor for looping
• Thinking *ngIf changes styles only
• Assuming *ngIf binds data to inputs

2. Which of the following is the correct syntax to conditionally display a paragraph only if isVisible is true?

easy

A. <p *ngIf="isVisible">Hello</p>

B. <p ngIf="isVisible">Hello</p>

C. <p *ngFor="isVisible">Hello</p>

D. <p *ngShow="isVisible">Hello</p>

Solution

1. Step 1: Identify the correct Angular directive syntax

   Angular uses *ngIf with an asterisk to indicate a structural directive.

2. Step 2: Check the attribute and expression format

   The expression should be inside quotes after *ngIf=, like *ngIf="isVisible".

3. Final Answer:

   <p *ngIf="isVisible">Hello</p> -> Option A

4. Quick Check:

   Use *ngIf with asterisk and quotes [OK]

Hint: Look for *ngIf with asterisk and quotes [OK]

Common Mistakes:

• Omitting the asterisk before ngIf
• Using ngIf without * (like ngIf="isVisible")
• Confusing *ngIf with *ngFor or *ngShow

3. Given this Angular template snippet:

<div *ngIf="showMessage">Welcome!</div>
<button (click)="showMessage = !showMessage">Toggle</button>

What happens when the button is clicked twice starting with showMessage = true?

medium

A. The message 'Welcome!' disappears after first click and reappears after second click.

B. The message 'Welcome!' stays visible all the time.

C. The message 'Welcome!' disappears and never comes back.

D. The button click causes an error because showMessage is not defined.

Solution

1. Step 1: Understand initial state and button action

   Initially, showMessage is true, so the <div> with 'Welcome!' is shown. Clicking the button toggles showMessage between true and false.

2. Step 2: Trace two clicks

   First click sets showMessage to false, hiding the message. Second click sets it back to true, showing the message again.

3. Final Answer:

   The message 'Welcome!' disappears after first click and reappears after second click. -> Option A

4. Quick Check:

   Toggle true/false shows/hides message [OK]

Hint: Toggle flips boolean, so message appears/disappears alternately [OK]

Common Mistakes:

• Assuming message never reappears after hiding
• Thinking button click causes error
• Believing message is always visible

4. Consider this Angular template:

<div *ngIf="user.isLoggedIn">Hello, {{user.name}}!</div>

But the app crashes with an error: Cannot read property 'isLoggedIn' of undefined. What is the best fix?

medium

A. Remove the *ngIf directive completely.

B. Change to *ngIf="user?.isLoggedIn" to safely check property.

C. Initialize user as an empty object in the component.

D. Use *ngIf="user.isLoggedIn === true" instead.

Solution

1. Step 1: Identify cause of error

   The error occurs because user is undefined when Angular tries to read user.isLoggedIn.

2. Step 2: Use safe navigation operator

   Using user?.isLoggedIn prevents error by checking if user exists before accessing isLoggedIn.

3. Final Answer:

   Change to *ngIf="user?.isLoggedIn" to safely check property. -> Option B

4. Quick Check:

   Use ? to avoid errors on undefined objects [OK]

Hint: Use ?. to safely access nested properties [OK]

Common Mistakes:

• Removing *ngIf loses conditional rendering
• Initializing user empty but not fixing undefined timing
• Checking equality without safe navigation still errors

5. You want to display a message only if a user has a non-empty email property and is verified (isVerified true). Which *ngIf expression correctly handles this?

hard

A. *ngIf="user.email == '' && user.isVerified"

B. *ngIf="user.email || user.isVerified"

C. *ngIf="user.email && user.isVerified"

D. *ngIf="user.email.length > 0 || user.isVerified"

Solution

1. Step 1: Understand the condition requirements

   The message should show only if user.email is not empty (truthy) AND user.isVerified is true.

2. Step 2: Analyze each option

   *ngIf="user.email && user.isVerified" uses logical AND to require both conditions true. *ngIf="user.email || user.isVerified" uses OR, which is incorrect. *ngIf="user.email == '' && user.isVerified" checks for empty string which is opposite of requirement. *ngIf="user.email.length > 0 || user.isVerified" uses OR and length check but allows message if only one condition is true.

3. Final Answer:

   *ngIf="user.email && user.isVerified" -> Option C

4. Quick Check:

   Use AND (&&) to require both conditions true [OK]

Hint: Use && to require both conditions true [OK]

Common Mistakes:

• Using || instead of && allowing partial matches
• Checking for empty string instead of truthy value
• Using length without checking for undefined user