Access modifiers in components in Angular - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

Effect of private modifier on component template binding

Consider this Angular component code snippet. What happens if you try to bind to a private property in the component's template?

Angular

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

@Component({
  selector: 'app-sample',
  template: `<p>{{ secretMessage }}</p>`
})
export class SampleComponent {
  private secretMessage = 'Hidden Text';
}

A The template will display nothing but no error will occur.

B The template will display 'Hidden Text' without any error.

C The template binding will cause a compilation error because private properties are not accessible in templates.

D The Angular compiler will convert the private property to public automatically.

💡 Hint

Think about how Angular templates access component properties and the role of access modifiers.

In Angular, templates can only bind to public properties and methods of the component class. Private or protected members are not accessible in the template and cause compilation errors.

❓ state_output

intermediate

Access modifier effect on component method call

Given this Angular component, what will be the output when the callMethod() is triggered from the template?

Angular

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

@Component({
  selector: 'app-demo',
  template: `<button (click)="callMethod()">Click</button>`
})
export class DemoComponent {
  private showMessage() {
    console.log('Hello from private method');
  }

  callMethod() {
    this.showMessage();
  }
}

A Console logs 'Hello from private method' when button is clicked.

B Compilation error because private methods cannot be called from public methods.

C Runtime error because private methods are inaccessible inside the class.

D Nothing happens because private methods are ignored.

💡 Hint

Remember how access modifiers work inside the same class.

Private methods are accessible within the same class. The public method 'callMethod' can call the private method 'showMessage' without any issue.

📝 Syntax

advanced

Identify the invalid access modifier usage in Angular component

Which of the following Angular component property declarations will cause a TypeScript syntax error?

A public title: string = 'Welcome';

B private _count: number = 0;

C protected data: any;

D internal info: string = 'data';

💡 Hint

Check which access modifiers are valid in TypeScript classes.

'internal' is not a valid TypeScript access modifier. Only public, private, and protected are allowed.

🔧 Debug

advanced

Why does this Angular component fail to compile?

This Angular component code fails to compile. What is the cause?

Angular

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

@Component({
  selector: 'app-test',
  template: `<p>{{ message }}</p>`
})
export class TestComponent {
  protected message = 'Hello';
}

A The template syntax is incorrect.

B Protected properties cannot be accessed in the template, causing a compilation error.

C The selector name is invalid and causes an error.

D Missing constructor causes compilation failure.

💡 Hint

Consider Angular template access rules for class members.

Angular templates can only bind to public members. Protected members are not accessible and cause compilation errors.

🧠 Conceptual

expert

Access modifiers and Angular's change detection

Which statement best describes how Angular's change detection interacts with component properties of different access modifiers?

A Angular tracks all properties regardless of access modifier because change detection works on the component instance.

B Only public and protected properties are tracked; private properties are excluded.

C Angular's change detection only tracks public properties; private and protected properties are ignored.

D Change detection requires properties to be decorated with @Input to track changes, access modifiers do not matter.

💡 Hint

Think about how Angular accesses component properties during change detection.

Angular's change detection runs on the component instance and can access all properties regardless of access modifier. Access modifiers affect TypeScript compile-time checks but do not restrict runtime property access.