Structural vs attribute directives in Angular - Quick Revision & Key Differences

Recall & Review

beginner

What is a structural directive in Angular?

A structural directive changes the layout by adding or removing elements in the DOM. It controls the structure of the view, like *ngIf or *ngFor.

beginner

What is an attribute directive in Angular?

An attribute directive changes the appearance or behavior of an existing element without changing the DOM structure. For example, ngClass or ngStyle.

beginner

How does *ngIf work as a structural directive?

*ngIf adds or removes elements from the DOM based on a condition. If the condition is false, the element is removed completely.

beginner

Can attribute directives add or remove elements from the DOM?

No, attribute directives only change how elements look or behave but do not add or remove elements from the DOM.

intermediate

Give an example of when to use a structural directive vs an attribute directive.

Use a structural directive like *ngFor to repeat elements or *ngIf to show/hide elements. Use an attribute directive like ngStyle to change colors or styles without changing the element itself.

Which Angular directive changes the DOM structure by adding or removing elements?

A Component

B Attribute directive

C Structural directive

D Service

Structural directives control the DOM layout by adding or removing elements.

Which directive type changes the style or behavior of an element without changing the DOM?

A Attribute directive

B Structural directive

C Pipe

D Module

Attribute directives modify appearance or behavior but do not change the DOM structure.

What does *ngIf do in Angular?

A Changes the style of an element

B Adds or removes elements based on a condition

C Repeats elements in a list

D Defines a new component

*ngIf conditionally adds or removes elements from the DOM.

Which of these is an example of an attribute directive?

A ngClass

B *ngIf

C ngModule

D *ngFor

ngClass changes the CSS classes of an element without changing the DOM.

Can attribute directives remove elements from the DOM?

A Yes, always

B Only if used with components

C Only in Angular 17+

D No, they only change appearance or behavior

Attribute directives do not remove or add elements; they only change how elements look or behave.

Explain the difference between structural and attribute directives in Angular.

Think about whether the directive adds/removes elements or just changes styles.

Describe a scenario where you would use a structural directive instead of an attribute directive.

When the page layout changes, structural directives are the choice.

Practice

1. Which of the following best describes a structural directive in Angular?

easy

A. It binds data to an element's property.

B. It changes the style of an element without altering the DOM structure.

C. It changes the layout by adding or removing elements from the DOM.

D. It listens to user events like clicks or key presses.

Solution

1. Step 1: Understand what structural directives do

   Structural directives modify the DOM layout by adding or removing elements dynamically.

2. Step 2: Compare with other directive types

   Attribute directives change appearance or behavior but do not add or remove elements.

3. Final Answer:

   It changes the layout by adding or removing elements from the DOM. -> Option C

4. Quick Check:

   Structural directive = changes DOM structure [OK]

Hint: Structural = add/remove elements; attribute = change style [OK]

Common Mistakes:

• Confusing attribute directives with structural directives
• Thinking attribute directives add or remove elements
• Mixing event listeners with directive types

2. Which of the following is the correct syntax for using the structural directive that repeats elements in Angular?

easy

A. <div *ngFor="let item of items">{{item}}</div>

B. <div [ngFor]="items">{{item}}</div>

C. <div (ngFor)="items">{{item}}</div>

D. <div #ngFor="items">{{item}}</div>

Solution

1. Step 1: Recall the syntax for the structural directive *ngFor

   The correct syntax uses an asterisk (*) before ngFor and a let variable to iterate.

2. Step 2: Check each option's syntax

   Only <div *ngFor="let item of items">{{item}}</div> uses *ngFor="let item of items" which is correct.

3. Final Answer:

   <div *ngFor="let item of items">{{item}}</div> -> Option A

4. Quick Check:

   *ngFor syntax = <div *ngFor="let item of items">{{item}}</div> [OK]

Hint: Structural directives use * before directive name [OK]

Common Mistakes:

• Using square brackets [] instead of * for structural directives
• Using parentheses () which are for events
• Using template reference (#) incorrectly

3. Given the following Angular template code, what will be rendered?

<ul>
  <li *ngIf="showItem">Item 1</li>
  <li>Item 2</li>
</ul>

Assuming showItem is false.

medium

A. No output, error occurs

B. Item 1Item 2

C.

D. Item 2

Solution

1. Step 1: Understand *ngIf behavior with false condition

   *ngIf removes the element from the DOM if the condition is false.

2. Step 2: Apply this to the template

   The first <li> with *ngIf="showItem" will not render because showItem is false. The second <li> renders normally.

3. Final Answer:

   <ul><li>Item 2</li></ul> -> Option D

4. Quick Check:

   *ngIf false removes element [OK]

Hint: *ngIf false means element is removed, not hidden [OK]

Common Mistakes:

• Thinking *ngIf hides element but keeps it in DOM
• Assuming both list items render regardless
• Confusing *ngIf with attribute directives

4. Identify the error in this Angular template snippet:

<button *ngIf="isEnabled" [disabled]="isDisabled">Click Me</button>

Assuming isEnabled and isDisabled are boolean variables.

medium

A. The syntax is correct; no error present.

B. The *ngIf directive must be replaced with [ngIf].

C. The [disabled] attribute should be replaced with *disabled.

D. Using *ngIf and [disabled] together on the same element is invalid.

Solution

1. Step 1: Check compatibility of *ngIf and [disabled]

   *ngIf controls element presence; [disabled] controls attribute binding. Both can coexist.

2. Step 2: Verify syntax correctness

   The syntax uses *ngIf with a boolean and [disabled] with a boolean, which is valid Angular syntax.

3. Final Answer:

   The syntax is correct; no error present. -> Option A

4. Quick Check:

   *ngIf and [disabled] can be used together [OK]

Hint: *ngIf controls element, [disabled] controls attribute independently [OK]

Common Mistakes:

• Thinking *ngIf and attribute bindings cannot be combined
• Confusing *ngIf with [ngIf]
• Replacing attribute bindings with structural directive syntax

5. You want to create a custom directive that highlights text by changing its background color when hovered. Which type of directive should you create and why?

hard

A. Structural directive, because it needs to add or remove elements on hover.

B. Attribute directive, because it changes the element's appearance without altering layout.

C. Structural directive, because it modifies the DOM structure dynamically.

D. Attribute directive, because it listens to user events but does not change styles.

Solution

1. Step 1: Understand the directive's purpose

   The directive changes background color on hover, affecting appearance only.

2. Step 2: Choose directive type based on behavior

   Attribute directives change element style or behavior without adding/removing elements, fitting this case.

3. Final Answer:

   Attribute directive, because it changes the element's appearance without altering layout. -> Option B

4. Quick Check:

   Appearance change = attribute directive [OK]

Hint: Appearance changes use attribute directives, layout changes use structural [OK]

Common Mistakes:

• Choosing structural directive for style changes
• Confusing event listening with directive type
• Thinking attribute directives add/remove elements