Template expressions and statements in Angular - Step-by-Step Execution

Concept Flow - Template expressions and statements

User interacts with template

↓

Template expression evaluated

↓

Value returned and displayed

↓

Template statement triggered

↓

Component method or action executed

↓

Component state updated

↓

Template re-evaluated with new state

User actions trigger template expressions to display values and statements to run component code, updating state and view.

Execution Sample

Angular

<!-- Template -->
<p>{{ counter }}</p>
<button (click)="increment()">Add</button>

// Component
counter = 0;
increment() { this.counter++; }

Shows a counter displayed with a template expression and a button that triggers a statement to increment it.

Execution Table

Step	Trigger	State Before	Action	State After	What Re-renders	DOM Change
1	Initial render	counter=0	Evaluate {{ counter }}	counter=0	<p> shows 0	<p>0</p> rendered
2	User clicks button	counter=0	Call increment()	counter=1	<p> shows 1	<p>1</p> updated
3	User clicks button again	counter=1	Call increment()	counter=2	<p> shows 2	<p>2</p> updated
4	No further clicks	counter=2	No action	counter=2	No re-render	DOM unchanged

💡 No more user actions, template expressions remain stable, no further updates.

Variable Tracker

Variable	Start	After 1	After 2	Final
counter	0	1	2	2

Key Moments - 2 Insights

Why does the displayed number update when I click the button?

Because the button triggers a template statement calling increment(), which changes the component's counter variable. This causes Angular to re-evaluate the template expression {{ counter }} and update the displayed value, as shown in execution_table steps 2 and 3.

Can I use complex logic inside {{ }} expressions?

No, template expressions should be simple and side-effect free. They only read values. Complex logic or state changes belong in template statements or component methods, as shown by the increment() method triggered by the button click.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of counter after the second button click?

A 2

B 0

C 1

D 3

💡 Hint

Check the 'State After' column at Step 3 in the execution_table.

At which step does the template expression {{ counter }} first update from 0 to 1?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look at the 'DOM Change' column in execution_table for when

changes from 0 to 1.

If the increment() method did not update counter, what would happen to the displayed number?

A It would decrease

B It would increase anyway

C It would stay the same

D It would show an error

💡 Hint

Refer to variable_tracker and execution_table showing state changes only happen when increment() updates counter.

Concept Snapshot

Template expressions {{ }} display component data in the view.
Template statements (e.g., (click)="method()") run component code on events.
Expressions must be simple and side-effect free.
Statements can change component state, triggering view updates.
Angular re-evaluates expressions when state changes.
Use expressions for display, statements for actions.

Full Transcript

In Angular templates, expressions inside double curly braces {{ }} show component data. When the component's data changes, Angular updates the displayed values automatically. Template statements, like (click)="increment()", run component methods when users interact, changing the component's state. This triggers Angular to re-evaluate expressions and update the view. Expressions should be simple and not change data. Statements handle actions and state changes. For example, a counter displayed with {{ counter }} updates when a button click calls increment(), increasing the counter and refreshing the display.