<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Rabin R on Medium]]></title>
        <description><![CDATA[Stories by Rabin R on Medium]]></description>
        <link>https://medium.com/@suriyarabin?source=rss-a10dd57bfd53------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*qrSYy4OG26Wb13wjtgPbKg.jpeg</url>
            <title>Stories by Rabin R on Medium</title>
            <link>https://medium.com/@suriyarabin?source=rss-a10dd57bfd53------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 13:09:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@suriyarabin/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Angular Signal Forms: Building Custom Controls the Modern Way]]></title>
            <link>https://medium.com/@suriyarabin/angular-signal-forms-building-custom-controls-the-modern-way-f3015d95a4e8?source=rss-a10dd57bfd53------2</link>
            <guid isPermaLink="false">https://medium.com/p/f3015d95a4e8</guid>
            <category><![CDATA[angular-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[angular]]></category>
            <dc:creator><![CDATA[Rabin R]]></dc:creator>
            <pubDate>Sat, 19 Sep 2026 10:57:38 GMT</pubDate>
            <atom:updated>2026-09-19T10:57:38.676Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zo66GF8GNMdpQerVaw1Fdg.png" /></figure><p>Modern Angular forms are moving toward a more reactive and type-safe model.</p><p>With Signal Forms, we can build forms around Angular Signals, define validation through schemas, and connect custom UI components directly to form state.</p><p>But the interesting part is this:</p><p><strong>What happens when a native </strong><strong>&lt;input&gt; is not enough?</strong></p><p>Maybe your application needs:</p><ul><li>A custom date picker</li><li>Phone number input</li><li>Currency input</li><li>OTP component</li><li>Searchable select</li><li>Tag selector</li><li>Rich text editor</li><li>Custom toggle</li><li>File uploader</li><li>Rating component</li></ul><p>This is where <strong>Custom Signal Form Controls</strong> become extremely useful.</p><h3>1. What are Angular Signal Forms?</h3><p>Signal Forms provide a signal-based approach to managing form state.</p><p>Instead of creating multiple FormControl and FormGroup instances, we start with a writable signal representing our form model.</p><pre>import { signal } from &#39;@angular/core&#39;;<br>import { form } from &#39;@angular/forms/signals&#39;;</pre><pre>interface LoginModel {<br>  email: string;<br>  password: string;<br>}</pre><pre>loginModel = signal&lt;LoginModel&gt;({<br>  email: &#39;&#39;,<br>  password: &#39;&#39;,<br>});</pre><pre>loginForm = form(this.loginModel);</pre><p>The form automatically creates a field tree that mirrors the model.</p><pre>loginForm.email<br>loginForm.password</pre><p>The field state exposes signals such as:</p><pre>loginForm.email().value()<br>loginForm.email().valid()<br>loginForm.email().invalid()<br>loginForm.email().touched()<br>loginForm.email().dirty()<br>loginForm.email().errors()</pre><p>This gives us a reactive foundation for form state.</p><p>Signal Forms require Angular 21 or newer, and they are included in @angular/forms.</p><h3>2. Why Custom Controls?</h3><p>Native controls already work:</p><pre>&lt;input [formField]=&quot;loginForm.email&quot; /&gt;</pre><p>But real applications often need custom UI.</p><p>For example:</p><pre>&lt;app-phone-input /&gt;</pre><p>or:</p><pre>&lt;app-date-picker /&gt;</pre><p>or:</p><pre>&lt;app-search-select /&gt;</pre><p>The challenge is making these components behave like normal form controls.</p><p>We want:</p><pre>Form Model<br>    ↓<br>Field Tree<br>    ↓<br>Custom Control<br>    ↓<br>User Interaction<br>    ↓<br>Updated Signal<br>    ↓<br>Form State</pre><p>Signal Forms provides dedicated interfaces for this.</p><h3>3. The Two Main Custom Control Interfaces</h3><p>Signal Forms provides two important interfaces:</p><h3>FormValueControl&lt;T&gt;</h3><p>Use this for controls that represent a single value.</p><p>Examples:</p><ul><li>Text input</li><li>Number input</li><li>Date picker</li><li>Select</li><li>Currency input</li><li>Phone input</li><li>Rating</li></ul><p>The control exposes:</p><pre>value = model&lt;T&gt;();</pre><h3>FormCheckboxControl</h3><p>Use this for boolean controls.</p><p>Examples:</p><ul><li>Checkbox</li><li>Toggle</li><li>Switch</li></ul><p>The control exposes:</p><pre>checked = model&lt;boolean&gt;();</pre><p>Angular’s [formField] directive detects these interfaces and connects the control to the field tree automatically.</p><h3>4. Building Our First Custom Control</h3><p>Let’s create a reusable custom input.</p><pre>import { Component, model } from &#39;@angular/core&#39;;<br>import { FormValueControl } from &#39;@angular/forms/signals&#39;;</pre><pre>@Component({<br>  selector: &#39;app-custom-input&#39;,<br>  standalone: true,<br>  template: `<br>    &lt;input<br>      type=&quot;text&quot;<br>      [value]=&quot;value()&quot;<br>      (input)=&quot;onInput($event)&quot;<br>    /&gt;<br>  `<br>})<br>export class CustomInput implements FormValueControl&lt;string&gt; {</pre><pre>  value = model(&#39;&#39;);</pre><pre>  onInput(event: Event) {<br>    const input = event.target as HTMLInputElement;</pre><pre>    this.value.set(input.value);<br>  }<br>}</pre><p>The important part is:</p><pre>implements FormValueControl&lt;string&gt;</pre><p>and:</p><pre>value = model(&#39;&#39;);</pre><p>The value model signal becomes the bridge between our custom component and Signal Forms.</p><h3>5. Connecting the Custom Control</h3><p>Now we can connect it using [formField].</p><pre>import { FormField } from &#39;@angular/forms/signals&#39;;</pre><pre>@Component({<br>  imports: [<br>    FormField,<br>    CustomInput<br>  ],<br>  template: `<br>    &lt;app-custom-input<br>      [formField]=&quot;registrationForm.email&quot;<br>    /&gt;<br>  `<br>})<br>export class RegistrationComponent {</pre><pre>  registrationModel = signal({<br>    email: &#39;&#39;<br>  });</pre><pre>  registrationForm = form(this.registrationModel);<br>}</pre><p>That’s the important architectural difference.</p><p>We don’t manually create a FormControl.</p><p>We don’t manually subscribe to valueChanges.</p><p>We don’t need a custom ControlValueAccessor.</p><p>The Signal Forms field system connects the component to the form.</p><h3>6. Custom Checkbox / Toggle</h3><p>For boolean controls, use:</p><pre>FormCheckboxControl</pre><p>Example:</p><pre>import {<br>  Component,<br>  model<br>} from &#39;@angular/core&#39;;</pre><pre>import {<br>  FormCheckboxControl<br>} from &#39;@angular/forms/signals&#39;;</pre><pre>@Component({<br>  selector: &#39;app-toggle&#39;,<br>  standalone: true,<br>  template: `<br>    &lt;button<br>      type=&quot;button&quot;<br>      [class.active]=&quot;checked()&quot;<br>      (click)=&quot;toggle()&quot;<br>    &gt;<br>      {{ checked() ? &#39;ON&#39; : &#39;OFF&#39; }}<br>    &lt;/button&gt;<br>  `<br>})<br>export class ToggleComponent<br>  implements FormCheckboxControl {</pre><pre>  checked = model(false);</pre><pre>  toggle() {<br>    this.checked.update(value =&gt; !value);<br>  }<br>}</pre><p>Then:</p><pre>&lt;app-toggle<br>  [formField]=&quot;settingsForm.notifications&quot;<br>/&gt;</pre><p>The important distinction is:</p><pre>FormValueControl<br>      ↓<br>value</pre><pre>FormCheckboxControl<br>      ↓<br>checked</pre><p>A FormValueControl should not expose checked, and a FormCheckboxControl should not expose value.</p><h3>7. Custom Control + Validation</h3><p>Validation belongs in the form schema.</p><p>For example:</p><pre>import {<br>  form,<br>  required,<br>  email<br>} from &#39;@angular/forms/signals&#39;;</pre><pre>registrationForm = form(<br>  this.registrationModel,<br>  path =&gt; {</pre><pre>    required(path.email);</pre><pre>    email(path.email);</pre><pre>  }<br>);</pre><p>Then:</p><pre>&lt;app-custom-input<br>  [formField]=&quot;registrationForm.email&quot;<br>/&gt;</pre><p>This separation is important.</p><h3>Avoid</h3><p>Putting business validation inside the custom component:</p><pre>isValid() {<br>  return this.value().length &gt; 5;<br>}</pre><h3>Prefer</h3><p>Keeping validation inside the form schema:</p><pre>required(path.email);</pre><pre>email(path.email);</pre><p>The custom control should primarily focus on <strong>UI + interaction</strong>.</p><p>The form schema should own <strong>validation + business rules</strong>.</p><p>This separation makes components more reusable.</p><h3>8. Reading Validation State Inside a Custom Control</h3><p>Signal Forms can provide state information to custom controls.</p><p>Useful state includes:</p><pre>disabled<br>readonly<br>hidden<br>invalid<br>errors<br>touched<br>dirty</pre><p>For example, your UI can react to:</p><pre>invalid()</pre><p>and display an error state.</p><p>Conceptually:</p><pre>Form Schema<br>     ↓<br>Validation<br>     ↓<br>Field State<br>     ↓<br>Custom Control<br>     ↓<br>UI Feedback</pre><p>This keeps the form state reactive instead of manually synchronizing it.</p><h3>9. Handling Touched State</h3><p>One important detail is blur handling.</p><p>For a custom control:</p><pre>touch = output&lt;void&gt;();</pre><p>Then:</p><pre>&lt;input<br>  [value]=&quot;value()&quot;<br>  (input)=&quot;onInput($event)&quot;<br>  (blur)=&quot;touch.emit()&quot;<br>/&gt;</pre><p>Why?</p><p>Because the form system needs to know when the user has left the control.</p><p>This becomes especially important when using rules such as:</p><pre>debounce(path.email, &#39;blur&#39;);</pre><p>Without a proper touch/blur event, blur-based behavior won’t work correctly.</p><h3>10. Reusable Custom Controls</h3><p>Imagine we build:</p><pre>UI Library<br>│<br>├── custom-input<br>├── phone-input<br>├── currency-input<br>├── date-picker<br>├── select<br>├── toggle<br>├── rating<br>└── tag-input</pre><p>Each component should have one responsibility.</p><p>For example:</p><pre>PhoneInputComponent<br>        │<br>        ├── UI<br>        ├── Formatting<br>        ├── User interaction<br>        └── FormValueControl&lt;string&gt;</pre><p>Then the application owns:</p><pre>Validation<br>Business Rules<br>API Integration<br>Submission</pre><p>This creates a cleaner architecture.</p><h3>11. Companion Validation Schemas</h3><p>A reusable control may also have common validation requirements.</p><p>For example, an email control might always require:</p><pre>required<br>email format</pre><p>Instead of repeating these rules everywhere, create a reusable schema.</p><pre>import {<br>  schema,<br>  required,<br>  email<br>} from &#39;@angular/forms/signals&#39;;</pre><pre>export const emailFieldSchema = schema&lt;string&gt;(path =&gt; {</pre><pre>  required(path, {<br>    message: &#39;Email is required&#39;<br>  });</pre><pre>  email(path, {<br>    message: &#39;Enter a valid email address&#39;<br>  });</pre><pre>});</pre><p>Then apply it:</p><pre>import {<br>  form,<br>  apply<br>} from &#39;@angular/forms/signals&#39;;</pre><pre>registrationForm = form(<br>  this.registrationModel,<br>  path =&gt; {</pre><pre>    apply(<br>      path.email,<br>      emailFieldSchema<br>    );</pre><pre>  }<br>);</pre><p>This allows the custom control and its validation rules to become a reusable package.</p><p>Angular’s documentation specifically recommends this companion-schema approach for reusable controls.</p><h3>12. Real-World Example: Phone Input</h3><p>A phone input is a good example of a custom control.</p><pre>@Component({<br>  selector: &#39;app-phone-input&#39;,<br>  standalone: true,<br>  template: `<br>    &lt;input<br>      type=&quot;tel&quot;<br>      [value]=&quot;value()&quot;<br>      (input)=&quot;onInput($event)&quot;<br>      (blur)=&quot;touch.emit()&quot;<br>    /&gt;<br>  `<br>})<br>export class PhoneInput<br>  implements FormValueControl&lt;string&gt; {</pre><pre>  value = model(&#39;&#39;);</pre><pre>  touch = output&lt;void&gt;();</pre><pre>  onInput(event: Event) {</pre><pre>    const input =<br>      event.target as HTMLInputElement;</pre><pre>    const formatted =<br>      input.value.replace(/\D/g, &#39;&#39;);</pre><pre>    this.value.set(formatted);<br>  }<br>}</pre><p>Now the component can be used like a normal Signal Form field:</p><pre>&lt;app-phone-input<br>  [formField]=&quot;profileForm.phone&quot;<br>/&gt;</pre><p>The consumer doesn’t need to know how the component internally formats the value.</p><h3>13. Real-World Example: Custom Rating Control</h3><p>Imagine a rating component:</p><pre>&lt;app-rating<br>  [formField]=&quot;reviewForm.rating&quot;<br>/&gt;</pre><p>The model:</p><pre>reviewModel = signal({<br>  rating: 0<br>});</pre><p>The component:</p><pre>export class RatingComponent<br>  implements FormValueControl&lt;number&gt; {</pre><pre>  value = model(0);</pre><pre>  setRating(rating: number) {<br>    this.value.set(rating);<br>  }<br>}</pre><p>Template:</p><pre>&lt;button<br>  type=&quot;button&quot;<br>  (click)=&quot;setRating(1)&quot;<br>&gt;<br>  ★<br>&lt;/button&gt;</pre><pre>&lt;button<br>  type=&quot;button&quot;<br>  (click)=&quot;setRating(2)&quot;<br>&gt;<br>  ★<br>&lt;/button&gt;</pre><p>The same pattern can be extended to:</p><ul><li>Star rating</li><li>Emoji rating</li><li>Slider</li><li>Color picker</li><li>Range selector</li></ul><h3>14. Signal Forms + Debouncing</h3><p>Search components are another good use case.</p><p>For example:</p><pre>searchForm = form(<br>  this.searchModel,<br>  path =&gt; {<br>    debounce(path.query, &#39;blur&#39;);<br>  }<br>);</pre><p>More advanced form logic can also control:</p><pre>disabled()<br>hidden()<br>readonly()<br>debounce()<br>metadata()</pre><p>based on reactive conditions.</p><p>This is useful for:</p><pre>Search fields<br>Autocomplete<br>Coupon validation<br>Dynamic forms<br>Conditional fields<br>API-backed inputs</pre><h3>15. Custom Controls vs ControlValueAccessor</h3><p>If you’ve worked with Angular Reactive Forms, you probably know:</p><pre>ControlValueAccessor</pre><p>The traditional architecture looks like:</p><pre>FormControl<br>      ↓<br>ControlValueAccessor<br>      ↓<br>Custom Component</pre><p>With Signal Forms:</p><pre>FieldTree<br>      ↓<br>FormField<br>      ↓<br>FormValueControl<br>      ↓<br>Custom Component</pre><p>For new Signal Form controls, Angular recommends the dedicated Signal Forms control interfaces rather than using ControlValueAccessor.</p><p>ControlValueAccessor remains useful for compatibility with existing reactive-form components.</p><p>Also, don’t implement both approaches on the same component.</p><p>Choose one integration model.</p><h3>16. Recommended Architecture</h3><p>For a large Angular application, I would structure reusable form controls like this:</p><pre>src/<br>└── app/<br>    └── shared/<br>        └── form-controls/<br>            ├── input/<br>            │   ├── input.component.ts<br>            │   ├── input.component.html<br>            │   └── input.component.scss<br>            │<br>            ├── phone-input/<br>            │   ├── phone-input.component.ts<br>            │   └── phone-input.schema.ts<br>            │<br>            ├── date-picker/<br>            │   ├── date-picker.component.ts<br>            │   └── date-picker.schema.ts<br>            │<br>            ├── select/<br>            ├── toggle/<br>            ├── rating/<br>            └── index.ts</pre><p>For a component library:</p><pre>@company/angular-form-controls</pre><p>could expose:</p><pre>export {<br>  PhoneInputComponent,<br>  phoneFieldSchema<br>};</pre><pre>export {<br>  DatePickerComponent<br>};</pre><pre>export {<br>  RatingComponent<br>};</pre><p>This makes the controls portable across applications.</p><h3>17. Best Practices</h3><h3>1. Keep the control focused</h3><p>The component should manage:</p><pre>UI<br>Interaction<br>Formatting<br>Value updates<br>Accessibility</pre><h3>2. Keep validation in schemas</h3><p>Use:</p><pre>required()<br>email()<br>minLength()<br>pattern()</pre><p>instead of embedding business rules inside the component.</p><h3>3. Prefer Signals</h3><p>Use:</p><pre>model()<br>input()<br>output()<br>computed()</pre><p>where appropriate.</p><h3>4. Handle blur correctly</h3><p>Custom controls should correctly communicate interaction state.</p><h3>5. Design for accessibility</h3><p>A custom control should still support:</p><pre>Keyboard navigation<br>Focus management<br>Labels<br>ARIA<br>Disabled state<br>Readonly state<br>Error messaging</pre><h3>6. Avoid unnecessary effects</h3><p>Don’t create effects simply to synchronize form state manually.</p><p>Let Signal Forms manage the state connection.</p><p>Angular’s documentation recommends using the form system’s state flow rather than registering custom effects for state management.</p><h3>18. One Important Mental Model</h3><p>The easiest way to understand Signal Forms Custom Controls is:</p><pre>               SIGNAL FORM<br>                     │<br>                     ▼<br>                 FieldTree<br>                     │<br>                     ▼<br>                 FormField<br>                     │<br>          ┌──────────┴──────────┐<br>          ▼                     ▼<br>   FormValueControl     FormCheckboxControl<br>          │                     │<br>          ▼                     ▼<br>       value()              checked()<br>          │                     │<br>          └──────────┬──────────┘<br>                     ▼<br>                  UI</pre><p>The custom component doesn’t own the entire form.</p><p>It owns its <strong>control UI and value interaction</strong>.</p><p>The form owns:</p><pre>Validation<br>State<br>Business rules<br>Form model<br>Submission</pre><p>That separation is what makes the architecture scalable.</p><h3>19. When Should You Use Custom Signal Form Controls?</h3><p>Use them when your UI is more complex than native HTML controls.</p><p>Good examples:</p><pre>✓ Date picker<br>✓ Phone input<br>✓ Currency input<br>✓ Searchable select<br>✓ OTP input<br>✓ Rating<br>✓ Tag selector<br>✓ Rich text editor<br>✓ Custom toggle<br>✓ File picker</pre><p>For a simple:</p><pre>&lt;input&gt;<br>&lt;select&gt;<br>&lt;textarea&gt;</pre><p>there is usually no reason to create a custom control.</p><p>Use the simplest control that solves the problem.</p><h3>20. Final Takeaway</h3><p>Angular Signal Forms are not just about replacing FormControl with Signals.</p><p>The bigger idea is <strong>composable form architecture</strong>.</p><p>With:</p><pre>signal()<br>    +<br>form()<br>    +<br>FormField<br>    +<br>FormValueControl<br>    +<br>FormCheckboxControl<br>    +<br>schema()</pre><p>we can build reusable, type-safe, reactive form controls without manually wiring every component through ControlValueAccessor.</p><p>The most important architectural principle is:</p><blockquote><strong><em>Let the custom control own the UI. Let the form schema own the rules. Let Signals connect the two.</em></strong></blockquote><p>That separation makes complex Angular forms easier to build, reuse, test, and maintain.</p><h3>What custom form control would you build first?</h3><p>📌 Date Picker<br>📌 Phone Input<br>📌 Searchable Select<br>📌 OTP Input<br>📌 Currency Input<br>📌 Rating Component</p><p>#Angular #Angular21 #Angular22 #SignalForms #AngularSignals #TypeScript #FrontendDevelopment #WebDevelopment #AngularDeveloper #SoftwareArchitecture</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f3015d95a4e8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Angular v22 is Here!  OnPush by Default, Signal Forms Official, AI Tooling & More]]></title>
            <link>https://medium.com/@suriyarabin/angular-v22-is-here-onpush-by-default-signal-forms-official-ai-tooling-more-fb7a893463c9?source=rss-a10dd57bfd53------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb7a893463c9</guid>
            <category><![CDATA[frontend-development]]></category>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[angular]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Rabin R]]></dc:creator>
            <pubDate>Sat, 06 Jun 2026 22:37:45 GMT</pubDate>
            <atom:updated>2026-06-06T22:37:45.262Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UjoTDwJt2yDJi40TgeYkYw.png" /></figure><p>The Angular team just dropped version 22 — and it genuinely feels like a new era.<br>We’re talking <em>OnPush</em> change detection as the default, <em>Signal Forms</em> graduating to the public API, AI‑ready developer tooling, and a ruthless cleanup of legacy APIs.</p><p>If you’ve been waiting for a release that makes Angular faster <em>out of the box</em>, more signal‑first, and more SSR‑friendly, this is it. Let’s dive in.</p><h3>🧠 Change Detection: OnPush Is Now the Norm</h3><p>This is the headline change.<br>In Angular v22, every new component automatically uses ChangeDetectionStrategy.OnPush unless you explicitly set something else. No more accidental default‑change‑detection‑for‑the‑whole‑tree nightmares.</p><pre>@Component({<br>  selector: &#39;app-user-card&#39;,<br>  template: `...`,<br>  // No changeDetection property needed – it&#39;s OnPush by default!<br>})<br>export class UserCardComponent {}</pre><p>If your app still depends on the old behavior, don’t worry. The team has renamed the previous default to ChangeDetectionStrategy.Eager:</p><pre>import { ChangeDetectionStrategy } from &#39;@angular/core&#39;;<br><br>@Component({<br>  selector: &#39;app-legacy-widget&#39;,<br>  template: `...`,<br>  changeDetection: ChangeDetectionStrategy.Eager,<br>})<br>export class LegacyWidgetComponent {}</pre><p>An automated migration is available, so you can switch to OnPush selectively and keep the rest on Eager until you’re ready. The message is clear: the Angular ecosystem is moving toward reactive, signal‑based rendering, and OnPush is the foundation.</p><h3>📋 Signal Forms Are Officially Here</h3><p>Forms powered by signals have graduated from experimental to the public API. This is huge for anyone building complex, reactive UIs.</p><p>New capabilities you can use today:</p><ul><li>reloadValidation() – Trigger validation manually without changing form values. Perfect when external data changes.</li><li>Debouncing for async validators — Both validateAsync() and validateHttp() now support built‑in debounce. No more manual debounceTime pipes.</li><li>FieldState.getError() – A clean, signal‑friendly way to access specific errors on any form field.</li><li>Template‑driven and reactive FVC support — Full Form Validation Context compatibility, so you can mix and match approaches seamlessly.</li></ul><p>Example of debounced async validation:</p><pre>const username = formControl(&#39;&#39;, {<br>  asyncValidators: [myValidator],<br>  asyncDebounceTime: 300, // 👈 new!<br>});</pre><p>Signal Forms now give you the same ergonomics as reactive forms but with fine‑grained reactivity and no RxJS boilerplate for simple cases.</p><h3>🌐 HttpClient: Fetch Is the Default, Better Progress Tracking</h3><p>Angular is finally cutting the cord on the legacy XhrBackend. Starting with v22, FetchBackend is the default for HttpClient.</p><ul><li>withFetch() is deprecated. You can remove it from your provideHttpClient() calls.</li><li>Upload progress tracking (which relies on XHR) now requires an explicit opt‑in:<br>provideHttpClient(withXhr()).</li><li>The reportProgress option has been split into two clear properties:<br>reportUploadProgress and reportDownloadProgress.</li></ul><p>This cleans up the API and pushes everyone toward the modern Fetch API, which brings better streaming support and smaller bundles.</p><h3>⚡ SSR &amp; Hydration: Incremental Hydration On by Default</h3><p>Incremental Hydration is no longer experimental. It’s enabled out of the box — zero configuration needed.</p><p>What does this mean?<br>Your app will hydrate progressively as users interact with it, rather than blocking the main thread to hydrate the entire page upfront.<br>Faster startup, better Core Web Vitals, and a smoother user experience — without changing a single line of code.</p><p>If you’re using Angular Universal or the new SSR story, v22 is a massive win.</p><h3>🤖 Angular + AI: First‑Class Developer Tooling</h3><p>Angular is investing heavily in AI and MCP (Model Context Protocol) tooling. Here’s what’s new:</p><ul><li>provideWebMcpTools() – Easily expose your app’s capabilities as MCP tools.</li><li>declareWebMcpTool() (experimental) – Declare individual tools with metadata.</li><li>AI runtime debugging tools — Inspect AI‑driven behavior directly in DevTools.</li><li>In‑page Dependency Injection graph — Visualize your DI tree with AI assistance, making debugging and optimization faster.</li></ul><p>Other AI‑adjacent improvements:</p><ul><li>Stable @Service decorator – Finally graduated, simplifying service definition.</li><li>injectAsync() helper – Resolve asynchronous dependencies cleanly.</li><li>Signal debouncing support — Already part of the signal RFC, now landing in core.</li><li>Resource caching for SSR — Reduces duplicate work when rendering on the server.</li><li>Bootstrap applications inside Shadow DOM roots — Great for micro‑frontends and web components.</li><li>TestBed.getLastFixture() – Handy helper for testing.</li></ul><p>Angular isn’t just “adding AI” — it’s building the infrastructure that makes AI‑assisted development, debugging, and optimization feel native.</p><h3>🧭 Router: Smarter Defaults, Cleaner API</h3><p>Several router improvements make navigation more predictable:</p><ul><li>paramsInheritanceStrategy now defaults to &#39;always&#39; – Route params are inherited by child routes without extra configuration.</li><li>currentSnapshot is required in CanMatchFn – A small breaking change that improves type safety.</li><li>New browserUrl input for router links – Gives you direct control over the URL displayed in the browser.</li><li>provideRoutes() has been removed – Migrate to provideRouter() (an automated migration is available).</li></ul><p>These changes clean up long‑standing confusion and edge cases.</p><h3>💔 Breaking Changes &amp; Removals</h3><p>Angular v22 continues the cleanup started in previous versions. These legacy APIs are gone for good:</p><ul><li>ComponentFactory – Removed. Use ViewContainerRef.createComponent() with component classes directly.</li><li>ComponentFactoryResolver – Removed. Same migration path.</li><li>createNgModuleRef() – Removed. Use createNgModule() instead.</li><li>checkNoChanges() – Removed. This was never a reliable way to detect changes.</li><li>Hammer.js integration — Removed entirely. If you need gesture support, use a dedicated library.</li></ul><p>Automated schematics will handle most migrations, but do a quick search through your codebase for any of these names.</p><h3>🛠 Platform &amp; Tooling</h3><p>Angular v22 is keeping pace with the ecosystem:</p><ul><li>Node.js 26 is supported (Node 24 still works, but 26 is the new target).</li><li>TypeScript 6.0 is now the minimum supported version. TypeScript 5.9 is no longer supported.</li><li>Build performance and CLI improvements continue behind the scenes.</li></ul><p>The TypeScript bump is significant — version 6.0 brings its own performance and type‑checking enhancements that Angular will leverage.</p><h3>🔮 Why v22 Feels Like a Milestone</h3><p>Put together, Angular v22 is more than a routine update. It’s:</p><ul><li>Faster by default (OnPush + Incremental Hydration)</li><li>Signal‑first (Forms, debouncing, resource caching)</li><li>SSR‑first (No‑config progressive hydration)</li><li>AI‑ready (MCP tooling, DI graph, debugging)</li><li>Lighter (Legacy APIs removed, Fetch default)</li></ul><p>This release removes a ton of baggage and sets the stage for the next evolution of the framework.</p><h3>🏁 How to Upgrade</h3><ol><li>Update your global Angular CLI:<br>npm install -g @angular/cli@latest</li><li>In your project:<br>ng update @angular/core@22 @angular/cli@22</li><li>Run the automated migrations:<br>They’ll handle ChangeDetectionStrategy.Eager, provideRouter(), and other deprecations.</li><li>Test — Especially if you relied on default change detection or Hammer.js.</li></ol><h3>💬 Final Thoughts</h3><p>Angular v22 is a gift to developers who want a modern, performant, and AI‑friendly framework without compromising the structure Angular is famous for. The shift to OnPush as the default alone will make thousands of apps faster overnight.</p><p>What are you most excited about? Signal Forms? Incremental Hydration? The AI tooling?<br>Drop a comment below — I’d love to hear how you plan to use these features.</p><p>If this post helped you, smash the clap 👏 button (50 claps tell Medium this is worth reading) and share it with your team. Let’s make the Angular community stronger together.</p><p>#Angular #AngularV22 #WebDevelopment #JavaScript #TypeScript #Frontend #Signals #SSR</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb7a893463c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Enhancing Accessibility in Angular Apps with Angular CDK (a11y)]]></title>
            <link>https://medium.com/@suriyarabin/enhancing-accessibility-in-angular-apps-with-angular-cdk-a11y-aea5cbf6aba0?source=rss-a10dd57bfd53------2</link>
            <guid isPermaLink="false">https://medium.com/p/aea5cbf6aba0</guid>
            <category><![CDATA[angular-aria]]></category>
            <category><![CDATA[web-accessibility]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Rabin R]]></dc:creator>
            <pubDate>Wed, 18 Mar 2026 14:00:19 GMT</pubDate>
            <atom:updated>2026-03-18T14:00:19.521Z</atom:updated>
            <content:encoded><![CDATA[<h3>Enhancing Accessibility in Angular Apps with Angular Aria</h3><p>Accessibility (a11y) ensures that web applications are usable by everyone, including people with disabilities. In Angular, building accessible apps is straightforward thanks to the Angular CDK’s a11y package — often referred to as Angular Aria. This package provides a set of utilities to help developers implement common accessibility patterns with minimal effort.</p><h3>What is Angular Aria?</h3><p>Angular Aria is part of the <a href="https://material.angular.io/cdk/a11y/overview">Angular Component Dev Kit (CDK)</a>. It offers services and directives that simplify managing focus, announcing messages to screen readers, trapping focus in modals, and more. It doesn’t replace semantic HTML or ARIA attributes but enhances them with programmatic control.</p><h3>Key Features</h3><ul><li>LiveAnnouncer — Programmatically announce messages to screen readers (e.g., “Item deleted”).</li><li>FocusMonitor — Track and monitor focus state of elements; useful for custom focus styling.</li><li>InteractivityChecker — Test if an element is visible, focusable, or disabled.</li><li>ListKeyManager — Manage keyboard navigation in lists (arrow keys, home/end).</li><li>FocusTrap — Trap focus inside a modal or dialog.</li><li>HighContrastModeDetector — Detect Windows High Contrast mode to adapt UI.</li></ul><h3>Getting Started</h3><p>First, install the Angular CDK:</p><pre>npm install @angular/cdk</pre><p>Then import the A11yModule into your module:</p><pre>import { A11yModule } from &#39;@angular/cdk/a11y&#39;;</pre><pre>@NgModule({<br>  imports: [A11yModule],<br>  ...<br>})<br>export class AppModule { }</pre><h3>Example: Using LiveAnnouncer</h3><p>Suppose you want to notify screen reader users when a new item is added to a list:</p><pre>import { LiveAnnouncer } from &#39;@angular/cdk/a11y&#39;;</pre><pre>@Component({...})<br>export class MyComponent {<br>  constructor(private liveAnnouncer: LiveAnnouncer) {}</pre><pre>  addItem() {<br>    // ... your logic ...<br>    this.liveAnnouncer.announce(&#39;Item added successfully&#39;, &#39;polite&#39;);<br>  }<br>}</pre><p>The announce method takes a message and a politeness setting (&#39;polite&#39; or &#39;assertive&#39;). The screen reader will read it when idle.</p><h3>Managing Focus with FocusMonitor</h3><p>Use FocusMonitor to detect when an element gains or loses focus:</p><pre>import { FocusMonitor } from &#39;@angular/cdk/a11y&#39;;</pre><pre>@Directive({...})<br>export class MyDirective {<br>  constructor(private focusMonitor: FocusMonitor, private elementRef: ElementRef) {<br>    this.focusMonitor.monitor(elementRef).subscribe(origin =&gt; {<br>      console.log(&#39;Focus origin:&#39;, origin); // &#39;mouse&#39;, &#39;keyboard&#39;, &#39;touch&#39;, or null<br>    });<br>  }<br>}</pre><p>This is perfect for applying different focus styles based on input method.</p><h3>Best Practices</h3><ol><li>Use semantic HTML — Start with &lt;button&gt;, &lt;nav&gt;, etc., before adding ARIA.</li><li>Bind ARIA attributes — Angular allows [attr.aria-label]=&quot;someValue&quot; directly in templates.</li><li>Test with screen readers — Tools like NVDA, VoiceOver, or ChromeVox.</li><li>Leverage Angular CDK — It handles many tricky a11y patterns out of the box.</li></ol><h3>Conclusion</h3><p>Accessibility is not an afterthought — it’s a core part of user experience. Angular Aria (via the CDK) gives you powerful, well-tested tools to make your apps inclusive without reinventing the wheel. Start using it today and make the web a better place for everyone.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aea5cbf6aba0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>