<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Directive Guides on AngularTS</title><link>https://angular-wave.github.io/angular.ts/docs/directives/</link><description>Recent content in Directive Guides on AngularTS</description><generator>Hugo</generator><language>en</language><atom:link href="https://angular-wave.github.io/angular.ts/docs/directives/index.xml" rel="self" type="application/rss+xml"/><item><title>Advanced directives: workers, WASM, channels, viewport</title><link>https://angular-wave.github.io/angular.ts/docs/directives/advanced/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://angular-wave.github.io/angular.ts/docs/directives/advanced/</guid><description>&lt;p>AngularTS ships several advanced directives that expose modern browser APIs — Web Workers, WebAssembly, Intersection Observer, and custom event channels — directly in HTML without requiring JavaScript. These directives are registered as part of the core &lt;code>ng&lt;/code> module and are available in every AngularTS application.&lt;/p>
&lt;h2 id="controller-and-scope-directives">Controller and scope directives&lt;a class="td-heading-self-link" href="#controller-and-scope-directives" aria-label="Heading self-link">&lt;/a>&lt;/h2>
&lt;h3 id="ng-controller">&lt;code>ng-controller&lt;/code>&lt;a class="td-heading-self-link" href="#ng-controller" aria-label="Heading self-link">&lt;/a>&lt;/h3>
&lt;p>Attaches a controller function to a section of the DOM, creating a new child scope populated by the controller.&lt;/p></description></item><item><title>Animation Directives: ng-animate-swap and CSS Hooks</title><link>https://angular-wave.github.io/angular.ts/docs/directives/animations/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://angular-wave.github.io/angular.ts/docs/directives/animations/</guid><description>&lt;p>AngularTS integrates animations into the same lifecycle that drives structural directives. Rather than managing &lt;code>setTimeout&lt;/code> calls or CSS transitions manually, you add the &lt;code>animate&lt;/code> attribute to an element and AngularTS&amp;rsquo;s &lt;code>$animate&lt;/code> service handles entry, exit, and class-change transitions — applying and removing CSS hook classes at the right moment in the digest cycle.&lt;/p>
&lt;h2 id="how-animate-integrates-with-directives">How &lt;code>$animate&lt;/code> integrates with directives&lt;a class="td-heading-self-link" href="#how-animate-integrates-with-directives" aria-label="Heading self-link">&lt;/a>&lt;/h2>
&lt;p>Structural directives — &lt;code>ng-if&lt;/code>, &lt;code>ng-repeat&lt;/code>, &lt;code>ng-show&lt;/code>, &lt;code>ng-hide&lt;/code>, &lt;code>ng-switch&lt;/code>, &lt;code>ng-include&lt;/code>, and &lt;code>ng-animate-swap&lt;/code> — all check whether an element carries animation data before manipulating the DOM. When the &lt;code>animate&lt;/code> attribute is present on an element (detected via &lt;code>hasAnimate(element)&lt;/code>), they delegate DOM operations to &lt;code>$animate&lt;/code> instead of performing them directly:&lt;/p></description></item><item><title>Data Binding Directives in AngularTS Explained</title><link>https://angular-wave.github.io/angular.ts/docs/directives/data-binding/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://angular-wave.github.io/angular.ts/docs/directives/data-binding/</guid><description>&lt;p>Data binding directives synchronise values between the scope and the DOM without requiring you to write event listeners or DOM queries by hand. AngularTS provides one-way and two-way binding variants to cover every use case, from safe text output to full form synchronisation.&lt;/p>
&lt;h2 id="ng-bind">ng-bind&lt;a class="td-heading-self-link" href="#ng-bind" aria-label="Heading self-link">&lt;/a>&lt;/h2>
&lt;p>&lt;code>ng-bind&lt;/code> is the attribute equivalent of double-curly interpolation (&lt;code>{{ }}&lt;/code>). It watches the given scope expression and writes the result as the element&amp;rsquo;s &lt;code>textContent&lt;/code>. Because it sets &lt;code>textContent&lt;/code>, it is immune to XSS — no HTML is ever parsed.&lt;/p></description></item><item><title>Form Directives and Validation in AngularTS</title><link>https://angular-wave.github.io/angular.ts/docs/directives/forms/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://angular-wave.github.io/angular.ts/docs/directives/forms/</guid><description>&lt;p>AngularTS treats HTML forms as first-class citizens of the framework. Every &lt;code>&amp;lt;form&amp;gt;&lt;/code> element (and &lt;code>ng-form&lt;/code> directive) creates a &lt;code>FormController&lt;/code> instance that tracks the aggregate validity and dirty state of all its inputs. Each input bound with &lt;code>ng-model&lt;/code> gets its own &lt;code>NgModelController&lt;/code> that manages the view-to-model pipeline, validation, and CSS class hooks.&lt;/p>
&lt;h2 id="the-form-directive">The form directive&lt;a class="td-heading-self-link" href="#the-form-directive" aria-label="Heading self-link">&lt;/a>&lt;/h2>
&lt;p>A plain &lt;code>&amp;lt;form&amp;gt;&lt;/code> element is enhanced by AngularTS into a &lt;code>FormController&lt;/code>. Give the form a &lt;code>name&lt;/code> attribute and the controller is published on the current scope under that name, giving you programmatic access to validation state.&lt;/p></description></item><item><title>HTTP Directives: ng-get, ng-post, ng-put, ng-sse</title><link>https://angular-wave.github.io/angular.ts/docs/directives/http/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://angular-wave.github.io/angular.ts/docs/directives/http/</guid><description>&lt;p>AngularTS ships a family of declarative HTTP directives inspired by HTMX. Rather than wiring up &lt;code>$http&lt;/code> calls in a controller, you attach &lt;code>ng-get&lt;/code>, &lt;code>ng-post&lt;/code>, &lt;code>ng-put&lt;/code>, &lt;code>ng-delete&lt;/code>, or &lt;code>ng-sse&lt;/code> directly to HTML elements. The directives handle the request lifecycle, DOM insertion, loading states, error handling, and scope merging — all configured through HTML attributes.&lt;/p>
&lt;h2 id="how-they-differ-from-http">How they differ from &lt;code>$http&lt;/code>&lt;a class="td-heading-self-link" href="#how-they-differ-from-http" aria-label="Heading self-link">&lt;/a>&lt;/h2>
&lt;p>When you use &lt;code>$http&lt;/code> directly you write controller code: define the request, subscribe to the promise, update scope properties, handle errors, and trigger a digest. The HTTP directives do all of this declaratively:&lt;/p></description></item><item><title>Directive Overview</title><link>https://angular-wave.github.io/angular.ts/docs/directives/overview/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://angular-wave.github.io/angular.ts/docs/directives/overview/</guid><description>&lt;p>Directives are how AngularTS attaches behavior and structure to HTML. A
directive is a marker on a DOM element or attribute that tells &lt;code>$compile&lt;/code> to
attach behavior, transform DOM, wire events, create scopes, or connect
controllers.&lt;/p>
&lt;p>Every built-in directive in AngularTS is applied as an HTML attribute using the
&lt;code>ng-&lt;/code> prefix. The compiler normalizes prefixes, so &lt;code>ng-bind&lt;/code>,
&lt;code>data-ng-bind&lt;/code>, and &lt;code>x-ng-bind&lt;/code> all match the same directive.&lt;/p>
&lt;p>Exact custom directive contracts live in TypeDoc:&lt;/p></description></item><item><title>Structural Directives: ng-if, ng-repeat, ng-switch</title><link>https://angular-wave.github.io/angular.ts/docs/directives/structural/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://angular-wave.github.io/angular.ts/docs/directives/structural/</guid><description>&lt;p>Structural directives reshape the DOM by adding, removing, or repeating elements. Unlike attribute directives that modify an existing element, structural directives use transclusion to stamp out or remove entire sections of the template. They run at high priority (600–1000) and set &lt;code>terminal: true&lt;/code> so that lower-priority directives do not compile until the structure is resolved.&lt;/p>
&lt;h2 id="ng-if">ng-if&lt;a class="td-heading-self-link" href="#ng-if" aria-label="Heading self-link">&lt;/a>&lt;/h2>
&lt;p>&lt;code>ng-if&lt;/code> conditionally includes or removes a DOM element based on a scope expression. When the expression becomes falsy, the element and its entire subtree — including child scopes and event listeners — are destroyed. When it becomes truthy again, a fresh element and child scope are created.&lt;/p></description></item></channel></rss>