Angular · Theory

Compiler

← All stacks

Theory

40/43

Compiler

Don’t start Compiler with jargon. Start with a Compiler dry-run. That is the whole point.

Do Compiler once by hand. one Compiler step Riya can write from memory. Change one input. Say the new result out loud.

Compiler exists so Riya can keep a Compiler dry-run correct in a small live site.

Compiler shows up in a small live site. Name a Compiler dry-run, not “a real-world scenario”.

Compiler trap — skipping the failure case for Compiler. Riya loses marks for that every viva.

After Compiler, Riya should still remember skipping the failure case for Compiler.

Close Compiler with — “If I skip it, a Compiler dry-run goes wrong like this: skipping the failure case for Compiler.”

Exam tip

For Compiler: definition + a small live site + one failure.

Example

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

@Component({
  selector: "app-root",
  template: `
    <h1>{{ title }}</h1>
    <button (click)="toggle()">Toggle</button>
    <p *ngIf="open">Panel open</p>
  `,
})
export class AppComponent {
  title = "Angular practice";
  open = true;
  toggle() {
    this.open = !this.open;
  }
}

Compiler: toggle open. Say whether the panel is on screen after one click.

Short notes

DefCompiler — Riya uses it for a Compiler dry-run in a small live site.
RuleCompiler → one Compiler step Riya can write from memory.
RememberCompiler + the Angular compiler (a small live site).
UseCompiler in a small live site (a Compiler dry-run).
TrapCompiler — skipping the failure case for Compiler.
ExCompiler → a Compiler dry-run.

import { Component } from "@angular/core"; @Component({ selector: "app-root", template: ` <h1>{{ title }}</h1> <button (click)="toggle()">Toggle</button> <p *ngIf="open">Panel open</p> `, }) export class AppComponent { title = "Angular practice"; open = true; toggle() { this.open = !this.open; } }

Compiler

Example

Short notes

Questions

Compiler

Example

Short notes

Questions