Why components are the building blocks in Angular - See It in Action

Why components are the building blocks

📖 Scenario: You are creating a simple Angular app to understand how components work as building blocks. Components help you organize your app into small, reusable pieces, just like building blocks in a toy set.

🎯 Goal: Build a basic Angular standalone component that displays a greeting message. This will show how components hold their own data and template, making them the building blocks of Angular apps.

📋 What You'll Learn

Create a standalone Angular component named GreetingComponent

Add a string variable message with the value 'Hello from Angular component!'

Use the @Component decorator with standalone: true

Display the message variable inside the component's template using interpolation

💡 Why This Matters

🌍 Real World

Angular components help developers build web apps by breaking the UI into small, manageable pieces that can be reused and maintained easily.

💼 Career

Understanding components is essential for Angular developers to create scalable and maintainable applications in professional environments.

1

Create the GreetingComponent with a message variable

Create a standalone Angular component named GreetingComponent. Inside the component class, create a string variable called message and set it to 'Hello from Angular component!'.

Angular

import { Component } from '@angular/core';

@Component({
  standalone: true,
  selector: 'app-greeting',
  template: ''
})
export class GreetingComponent {
  // Your code here
}

Hint

Use message: string = 'Hello from Angular component!'; inside the class.

2

Add the component template to display the message

In the @Component decorator, set the template property to display the message variable using Angular interpolation syntax {{ message }}.

Angular

import { Component } from '@angular/core';

@Component({
  standalone: true,
  selector: 'app-greeting',
  template: '' // Add interpolation here
})
export class GreetingComponent {
  message: string = 'Hello from Angular component!';
}

Hint

Use template: '{{ message }}' to show the message in the HTML.

3

Add the selector to use the component in HTML

Make sure the @Component decorator has the selector property set to 'app-greeting'. This lets you use the component as an HTML tag <app-greeting></app-greeting>.

Angular

import { Component } from '@angular/core';

@Component({
  standalone: true,
  selector: 'app-greeting', // Confirm selector here
  template: '{{ message }}'
})
export class GreetingComponent {
  message: string = 'Hello from Angular component!';
}

Hint

The selector should be 'app-greeting' to use the component as <app-greeting></app-greeting>.

4

Use the GreetingComponent in an Angular app template

In your main app component or HTML file, add the <app-greeting></app-greeting> tag to display the greeting message from the GreetingComponent.

Angular

Hint

Use the component selector as an HTML tag: <app-greeting></app-greeting>.

Practice

1. Why are components considered the building blocks in Angular applications?

easy

A. Because they split the app into small, manageable pieces with their own HTML, CSS, and logic.

B. Because they replace the need for services and modules entirely.

C. Because they only contain CSS styles for the app.

D. Because they are used only for routing between pages.

Solution

1. Step 1: Understand the role of components

   Components divide the app into smaller parts, each with its own structure and behavior.

2. Step 2: Recognize what components contain

   Each component has its own HTML, CSS, and logic, making the app easier to build and maintain.

3. Final Answer:

   Because they split the app into small, manageable pieces with their own HTML, CSS, and logic. -> Option A

4. Quick Check:

   Components = small parts with own code [OK]

Hint: Components bundle HTML, CSS, and logic into small parts [OK]

Common Mistakes:

• Thinking components only hold styles
• Confusing components with services
• Believing components handle routing only

2. Which of the following is the correct way to define a basic Angular component?

easy

A. function SampleComponent() { selector: 'app-sample' }

B. @Component({ selector: 'app-sample', templateUrl: './sample.html' }) export class SampleComponent {}

C. @Component({ selector: 'app-sample' }) function SampleComponent() {}

D. class SampleComponent { selector = 'app-sample' }

Solution

1. Step 1: Identify Angular component syntax

   Angular components use the @Component decorator with metadata like selector and templateUrl.

2. Step 2: Check the class declaration

   The component must be a class exported with the decorator above it.

3. Final Answer:

   @Component({ selector: 'app-sample', templateUrl: './sample.html' }) export class SampleComponent {} -> Option B

4. Quick Check:

   @Component decorator + class = correct syntax [OK]

Hint: Look for @Component decorator above an exported class [OK]

Common Mistakes:

• Using function instead of class for components
• Missing @Component decorator
• Placing selector inside class body without decorator

3. Given this Angular component template:

<h1>{{title}}</h1>
<p>Welcome to {{appName}}!</p>

and this component class:

export class WelcomeComponent {
  title = 'Hello';
  appName = 'MyApp';
}

What will be the rendered output in the browser?

medium

A. HelloWelcome to {{appName}}!

B. {{title}}Welcome to {{appName}}!

C. HelloWelcome to MyApp!

D. {{title}}Welcome to MyApp!

Solution

1. Step 1: Understand Angular interpolation

   Angular replaces {{variable}} with the variable's value from the component class.

2. Step 2: Substitute variables in the template

   title = 'Hello' and appName = 'MyApp', so the template renders with these values.

3. Final Answer:

   <h1>Hello</h1><p>Welcome to MyApp!</p> -> Option C

4. Quick Check:

   Interpolation replaces variables with values [OK]

Hint: Remember {{}} shows variable values in template [OK]

Common Mistakes:

• Thinking {{}} stays as text in output
• Mixing variable names or values
• Ignoring component class properties

4. Identify the error in this Angular component code:

@Component({
  selector: 'app-test',
  template: '<p>Test works!</p>'
})
export class TestComponent {
  title = 'Test';
  constructor() {
    this.title = 123;
  }
}

medium

A. Assigning a number to a string property 'title' causes a type error.

B. Missing @Injectable decorator on the class.

C. Template string should use backticks instead of single quotes.

D. Selector name 'app-test' is invalid.

Solution

1. Step 1: Check property type consistency

   title is initialized as a string 'Test', but later assigned a number 123, which is a type mismatch.

2. Step 2: Verify other parts for errors

   @Injectable is not required for components, template string with single quotes is valid, and selector 'app-test' is valid.

3. Final Answer:

   Assigning a number to a string property 'title' causes a type error. -> Option A

4. Quick Check:

   Property type mismatch = error [OK]

Hint: Check if property types stay consistent in constructor [OK]

Common Mistakes:

• Thinking @Injectable is needed for components
• Believing template string quotes cause error
• Assuming selector names must be different

5. You want to build a dashboard app with multiple sections like header, sidebar, and content. Why should you use components for each section instead of writing all HTML and logic in one file?

hard

A. Because writing all code in one file is faster and recommended for large apps.

B. Because Angular requires every section to be a separate component by default.

C. Because components automatically improve app speed without any extra work.

D. Because components let you reuse, maintain, and test each section separately, making the app easier to manage.

Solution

1. Step 1: Understand component benefits

   Components break the app into smaller parts that can be reused, tested, and maintained independently.

2. Step 2: Compare with single-file approach

   Writing all code in one file makes it hard to manage, debug, and update as the app grows.

3. Final Answer:

   Because components let you reuse, maintain, and test each section separately, making the app easier to manage. -> Option D

4. Quick Check:

   Components improve manageability and reuse [OK]

Hint: Use components to split and manage app parts easily [OK]

Common Mistakes:

• Thinking Angular forces components for every section
• Believing components alone boost speed automatically
• Assuming one big file is better for large apps