Skip to main content

What are custom structural directives? How do you implement one?

๐Ÿงฑ What Are Structural Directives?

Structural directives are used to change the structure of the DOM — by adding, removing, or manipulating elements in the template.

Examples of built-in structural directives:

  • *ngIf

  • *ngFor

  • *ngSwitch

They use the * prefix and typically manipulate the host element and its view in the DOM.

What are custom structural directives? How do you implement one?

๐Ÿงฐ What Are Custom Structural Directives?

A custom structural directive lets you create your own logic to control how and when certain parts of the DOM appear.

For example, a custom directive called *appUnless could behave as the opposite of *ngIf.

✅ How to Implement One — Step-by-Step

๐Ÿงช Example: *appUnless Directive

1. Create the Directive

ng generate directive unless

2. Code Implementation

import { Directive, Input, TemplateRef, ViewContainerRef } from '@angular/core'; @Directive({ selector: '[appUnless]' }) export class UnlessDirective { constructor( private templateRef: TemplateRef<any>, private viewContainer: ViewContainerRef ) {} @Input() set appUnless(condition: boolean) { if (!condition) { this.viewContainer.createEmbeddedView(this.templateRef); // Show it } else { this.viewContainer.clear(); // Remove it } } }

๐Ÿ’ก How It Works:

  • TemplateRef: Represents the element the directive is applied to.

  • ViewContainerRef: Container that holds views — allows us to insert or remove them.

  • @Input(): Binds the directive’s value (like *appUnless="isLoggedIn").

๐Ÿงช Usage in Template

<div *appUnless="isLoggedIn"> Please log in to view this content. </div>

If isLoggedIn is false, the content appears — the reverse of *ngIf.

๐Ÿง  Summary

AspectStructural Directive
Modifies DOM?✅ Yes — adds/removes elements dynamically
PrefixTypically used with *
UsesTemplateRef, ViewContainerRef, @Input
Example*ngIf, *ngFor, *appUnless

 

Popular posts from this blog

How does BGP prevent routing loops? Explain AS_PATH and loop prevention mechanisms.

 In Border Gateway Protocol (BGP), preventing routing loops is critical — especially because BGP is the inter-domain routing protocol used to connect Autonomous Systems (ASes) on the internet. ๐Ÿ”„ How BGP Prevents Routing Loops The main mechanism BGP uses is the AS_PATH attribute . ๐Ÿ” What is AS_PATH? AS_PATH is a BGP path attribute that lists the sequence of Autonomous Systems (AS numbers) a route has traversed. Each time a route is advertised across an AS boundary, the local AS number is prepended to the AS_PATH. Example: If AS 65001 → AS 65002 → AS 65003 is the route a prefix has taken, the AS_PATH will look like: makefile AS_PATH: 65003 65002 65001 It’s prepended in reverse order — so the last AS is first . ๐Ÿšซ Loop Prevention Using AS_PATH ✅ Core Mechanism: BGP routers reject any route advertisement that contains their own AS number in the AS_PATH. ๐Ÿ” Why It Works: If a route makes its way back to an AS that’s already in the AS_PATH , that AS kno...

Explain the Angular compilation process: View Engine vs. Ivy.

 The Angular compilation process transforms your Angular templates and components into efficient JavaScript code that the browser can execute. Over time, Angular has evolved from the View Engine compiler to a newer, more efficient system called Ivy . Here's a breakdown of the differences between View Engine and Ivy , and how each affects the compilation process: ๐Ÿ”ง 1. What Is Angular Compilation? Angular templates ( HTML inside components) are not regular HTML—they include Angular-specific syntax like *ngIf , {{ }} interpolation, and custom directives. The compiler translates these templates into JavaScript instructions that render and update the DOM. Angular uses Ahead-of-Time (AOT) or Just-in-Time (JIT) compilation modes: JIT : Compiles in the browser at runtime (used in development). AOT : Compiles at build time into efficient JS (used in production). ๐Ÿงฑ 2. View Engine (Legacy Compiler) ➤ Used in Angular versions < 9 ๐Ÿ” How It Works: Compiles templat...

What is Zone.js, and why does Angular rely on it?

Zone.js is a library that Angular relies on to manage asynchronous operations and automatically trigger change detection when necessary. Think of it as a wrapper around JavaScript’s async APIs (like setTimeout , Promise , addEventListener , etc.) that helps Angular know when your app's state might have changed. ๐Ÿ” What is Zone.js? Zone.js creates an execution context called a "Zone" that persists across async tasks. It tracks when tasks are scheduled and completed—something JavaScript doesn't do natively. Without Zone.js, Angular wouldn’t automatically know when user interactions or async events (like an HTTP response) occur. You’d have to manually tell Angular to update the UI. ⚙️ Why Angular Uses Zone.js ✅ 1. Automatic Change Detection Zone.js lets Angular detect when an async task finishes and automatically run change detection to update the UI accordingly. Example: ts setTimeout ( () => { this . value = 'Updated!' ; // Angular know...