Access modifiers in components in Angular

Introduction

Access modifiers control who can use or change parts of a component. They help keep your code safe and organized.

When you want to hide some details inside a component so others can't change them by mistake.

When you want to allow only certain parts of your app to use or change a value or function.

When you want to make your component easier to understand by showing only important parts.

When you want to protect data inside a component from being changed directly.

When you want to share some data or functions with templates but keep others private.

Syntax

Angular

class MyComponent {
  public name: string;    // accessible everywhere
  private secret: string; // accessible only inside this class
  protected age: number;  // accessible inside this class and subclasses
}

public means anyone can access it.

private means only the component itself can access it.

protected means the component and its child classes can access it.

Examples

This component has a public username anyone can see, a private password only inside the component, and a protected role for child classes.

Angular

export class UserComponent {
  public username = 'Alice';
  private password = '1234';
  protected role = 'admin';
}

The price is private but can be read using the public getPrice() method.

Angular

export class ProductComponent {
  private price = 100;
  public getPrice() {
    return this.price;
  }
}

Sample Program

This Angular component shows how public and private access modifiers work. The template can show publicInfo directly but cannot access secretInfo directly. Instead, it uses a public method getSecret() to get the private data.

Angular

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

@Component({
  selector: 'app-sample',
  template: `<p>{{ publicInfo }}</p><p>{{ getSecret() }}</p>`
})
export class SampleComponent {
  public publicInfo = 'Visible to everyone';
  private secretInfo = 'Hidden from template';

  public getSecret() {
    return this.secretInfo;
  }
}

Important Notes

Templates can only access public members of the component.

Use private to hide details that should not be changed outside the component.

protected is useful when you extend components and want child classes to access some members.

Summary

Access modifiers control visibility and safety of component parts.

public is open to all, private is hidden inside the component, and protected is for the component and its children.

Templates can only use public members directly.

Practice

1. Which access modifier allows a component property to be used directly in its template in Angular?

easy

A. readonly

B. private

C. protected

D. public

Solution

1. Step 1: Understand template access rules

   Angular templates can only access properties and methods marked as public.

2. Step 2: Compare access modifiers

   private and protected members are not accessible in templates, only public members are.

3. Final Answer:

   public -> Option D

4. Quick Check:

   Templates access public members only [OK]

Hint: Templates can only see public members [OK]

Common Mistakes:

• Thinking private members are accessible in templates
• Confusing protected with public for template access
• Assuming readonly affects visibility

2. Which of the following is the correct syntax to declare a private property named count in an Angular component?

easy

A. count private: number;

B. private count: number;

C. protected count = number;

D. public count: number;

Solution

1. Step 1: Recall TypeScript property declaration syntax

   Access modifier comes first, then property name, colon, and type.

2. Step 2: Check each option

   private count: number; matches correct syntax: private count: number;. public count: number; is public, not private. protected count = number; has wrong assignment syntax. count private: number; has wrong order.

3. Final Answer:

   private count: number; -> Option B

4. Quick Check:

   Access modifier + name + colon + type [OK]

Hint: Access modifier comes before property name [OK]

Common Mistakes:

• Placing access modifier after property name
• Using assignment instead of type annotation
• Mixing up protected and private keywords

3. Consider this Angular component snippet:

export class MyComponent {
  private secret = 'hidden';
  public visible = 'shown';
}

Which property can be accessed in the component's template?

medium

A. secret

B. Both secret and visible

C. visible

D. Neither secret nor visible

Solution

1. Step 1: Identify access modifiers of properties

   secret is private, visible is public.

2. Step 2: Recall template access rules

   Templates can only access public members, so only visible is accessible.

3. Final Answer:

   visible -> Option C

4. Quick Check:

   Only public properties are template-accessible [OK]

Hint: Only public properties show in templates [OK]

Common Mistakes:

• Assuming private properties are accessible in templates
• Thinking both properties are accessible
• Confusing private with protected

4. Identify the error in this Angular component code:

export class DemoComponent {
  private title = 'Hello';
}

// In template:
// <h1>{{ title }}</h1>

medium

A. Template cannot access private property 'title'

B. No error, code works fine

C. Missing semicolon after title declaration

D. title should be declared as protected

Solution

1. Step 1: Check property access modifier

   title is declared private, so it is hidden from outside the class.

2. Step 2: Understand template access rules

   Angular templates can only access public properties, so trying to use title in template causes an error.

3. Final Answer:

   Template cannot access private property 'title' -> Option A

4. Quick Check:

   Private properties are not accessible in templates [OK]

Hint: Templates only see public, not private properties [OK]

Common Mistakes:

• Ignoring access modifier effect on templates
• Thinking missing semicolon causes error
• Confusing protected with private for template access

5. You want a property data in a base Angular component to be accessible in its child components but not directly in the template. Which access modifier should you use?

hard

A. protected

B. private

C. public

D. readonly

Solution

1. Step 1: Understand access modifier meanings

   private hides from all except the class itself, public exposes everywhere including templates, protected allows access in the class and its subclasses but not templates.

2. Step 2: Match requirement to modifier

   Since data should be accessible in child components but hidden from templates, protected fits perfectly.

3. Final Answer:

   protected -> Option A

4. Quick Check:

   Protected = accessible in children, hidden from templates [OK]

Hint: Use protected for child access, hide from templates [OK]

Common Mistakes:

• Choosing public and exposing property to templates
• Using private and blocking child access
• Confusing readonly with access control